| Age | Commit message (Collapse) | Author |
|---|
|
an offset/size/address by shifting by PAGE_SHIFT. Make uvm_objwrire/unwire
use voff_t instead of off_t. The former is the right type here even if it is
equivalent to the latter.
Inspired by a somewhat similar changes in Bitrig.
ok deraadt@, guenther@
|
|
Forgotten during yesterday's STRICT_ALIGNMENT cleanup commit.
|
|
|
|
|
|
|
|
cast bus_space_tag_t to (u_long)
|
|
ok jsg@
"go for it" kettenis@
|
|
|
|
|
|
handling.
Confusion with "NTP Server?" reported by Xavier Claude via misc@.
ok rpe@ halex@
|
|
unsupported mark/marked combination in a single rule.
ok andre@
|
|
|
|
|
|
the test file.
ok reyk
|
|
amusingly, theo phrased this with considerably more restraint than i did.
|
|
"fire bomb" tedu@
|
|
|
|
is amusing.
ok deraadt@
|
|
|
|
|
|
|
|
Now that aborting interrupt pipes does not prevent us from freeing
the associated xfer, make sure to flag this xfer as "done" even if
there's no need to abort it in hardware.
|
|
|
|
Actually, there seems to be no PC-9801 extension board slot on
'original' LUNA-88K.
ok miod@
|
|
|
|
ok reyk@
|
|
okay reyk@
|
|
|
|
previous proc.c update
ok reyk@
|
|
ok miod@
|
|
|
|
|
|
|
|
|
|
|
|
Nothing use them for the moment, but here is the plan:
Since a route lookup is always necessary to output a packet it makes
sense to store all the information regarding how the packet should be
sent in the routing entry. This will save us some expensive lookups
on address lists.
But once we have all the information about our addresses in the routing
table, we can even use it in the input path with the hope that the number
of lookups in the forwarding case can be reduce to one.
ok henning@, chris@
|
|
normally does nothing), from Marcel Partap.
|
|
instead. Means modifier keys still increase the line count, just not as
much. Based on a diff from Marcel Partap.
|
|
the env vars section; tidy up the env vars section and remove the commented
out stuff which relataes mainly to less on other systems;
|
|
- Xr more 1
ok millert schwarze
|
|
|
|
|
|
irritating flaws:
a) The old way of always using the top or left if the choice is
ambiguous is annoying when the layout is unbalanced.
b) The new way of remembering the last used pane is annoying if the
layout is balanced and the leftmost is obvious to the user (because
clearly if we go right from the top-left in a tiled set of four we want
to end up in top-right, even if we were last using the bottom-right).
So instead, use a combination of both: if there is only one possible
pane alongside the current pane, move to it, otherwise choose the most
recently used of the choice.
|
|
|
|
than defining it for not (i386 and amd64 (and sometimes s390)) only.
Compile-time tests remain compile-time tests, and runtime-test remain
runtime-test instead of being converted to compile-time tests, per matthew@'s
explicit demand (rationale: this makes sure the compiler checks your code even
if you won't run it).
No functional change except on s390 (which we don't run on) and vax (which we
run on, but noone cares about)
ok matthew@
|
|
When you don't get what you asked for, you get angry.
When you add a tiny bit, it should be "more" or "less" still,
or you'll get angry.
So lets make zmore(1) call more(1) and zless(1) call less(1),
as it's supposed to be.
okay and input from ingo@, no objections from author AKA millert@
|
|
|
|
Since _PATH_MASTERPASSWD_LOCK is on a local file system in any sane setup
and written to in blocking mode, i don't see how write(2) could return
before having written everything, so this maybe wasn't an actual bug,
but it should be repaired anyway, if only for clarity and extra safety.
From Ben Cornett <ben at lantern dot is>;
ok millert@.
|
|
reported to openssl by David Ramos (rt 3338)
stealing commit from logan, who's run away. ok miod.
|
|
i've never worked on codebase so resistant to efforts to improve it.
|
