| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
struct pam_conv takes a void * for the appdata_ptr but is being passed
a const char * - explicitly cast away the const
|
|
|
|
|
| |
PR: docs/114731
Submitted by: Matthew Seaman <m.seaman@infracaninophile.co.uk>
|
|
|
|
|
|
|
| |
case-sensitivity
PR: docs/117593
Submitted by: Nikolay Bachiyski <nbachiyski@developer.bg>
|
|
|
|
|
|
|
|
|
|
| |
- Use PTY* for all pty(4) related constants.
- Use PTMX* for all pts(4) related constants.
- Consistently use _PATH_DEV PTMX rather than "/dev/ptmx".
- Revert 1.7 and properly fix it by using the correct prefix string for
pts(4) masters.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Start mergemaster
2. Interrupt it
3. < Somehow the temproot directory disappears >
4. mergemaster -r
Many bad things can happen, especially if the -i option is in use.
Therefore, add a check to make sure it still exists before we start
comparing files.
Brought to my attention by:
PR: bin/40538
Submitted by: Cyrille Lefevre <cyrille.lefevre@laposte.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
old code special cased them too early which caused a few differences for
these sort of links relative to other PCI links:
- They were always re-routed via the BIOS call instead of assuming that
they were already routed if the BIOS had programmed the IRQ into a
matching device during POST.
- If the BIOS did route that link to a different IRQ that was marked as
invalid, we trusted the $PIR table rather than the BIOS IRQ.
This change moves the special casing for "unique IRQ" links to only take
that into account when picking an IRQ for an unrouted link so that these
links will now not be routed if the BIOS appears to have routed it already
(some BIOSen have problems with that) and so that if the BIOS uses a
different IRQ than the $PIR, we trust the BIOS routing instead (this is
what we do for all other links as well).
Reported by: Bruce Walter walter of fortean com
MFC after: 1 week
|
| |
|
|
|
|
| |
which included commits to RCS files with non-trunk default branches.
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This turns out to be due to an argument botch for hid_report_size.
The PR contained patches to fix the argument botch.
Submitted by: Maurice Castro
PR: usb/118915
|
| | |
|
| |
| |
| |
| | |
passing literal strings to the constructors of string.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
page to be in the free lists. Instead, it now returns TRUE if it
removed the page from the free lists and FALSE if the page was not
in the free lists.
This change is required to support superpage reservations. Specifically,
once reservations are introduced, a cached page can either be in the
free lists or a reservation.
|
| |
| |
| |
| |
| |
| |
| | |
bus_activate_resource() methods instead of splitting it up between
bus_alloc_resource() and bus_activate_resource().
Glanced at by: marcel
|
| |
| |
| |
| | |
Submitted by: Achim Leubner @ Adaptec.
|
| |
| |
| |
| |
| |
| |
| |
| | |
kick off any other users on the device line before using it since
openpty(3) is documented to do this. Note that grantpt(3) does not
call revoke(2), it only adjusts permissions and ownership.
MFC after: 3 days
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
version number, as it is named after that
PR: docs/118053
Submitted by: Michael Plass <mfp49_freebsd@plass-family.net>
|
| | |
|
| | |
|
| |
| |
| |
| | |
(Repocopied from src/tools/tools/ministat)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
as multicast/broadcast frames. Previously re(4) ignored multicast
frames in promiscuous mode. The RTL8169 datasheet was not clear
how it handles multicast frames in promiscuous mode.
PR: kern/118572
MFC after: 3 days
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
bde is going to commit logl() Real Soon Now.
I'm just trying to slow him down with merge conflicts.
Noticed by: bde
|
| |
| |
| |
| |
| | |
Submitted by: "Paul B. Mahol" <onemda@gmail.com>
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| | |
NULL and doesn't point to a NULL pointer before dereferencing it. This
fixes a panic triggered by Xorg 7.3.
Reported and tested by: Bill Green
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| | |
committed yet, but the declaration leaked in when I added nan() and
friends.
Reported by: pav
|
| | |
|
| |
| |
| |
| |
| | |
At present, this error is inconsequential; the other half of the loop
continuation condition is sufficient to achieve correct execution.
|
| |
| |
| |
| | |
bits per second ones.
|
| |
| |
| |
| | |
there's nothing allocated at all yet.
|
| |
| |
| |
| |
| |
| | |
line break.
MFC after: 3 days
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a pointer to struct bus_space. The structure contains function
pointers that do the actual bus space access.
The reason for this change is that previously all bus space
accesses were little endian (i.e. had an explicit byte-swap
for multi-byte accesses), because all busses on Macs are little
endian.
The upcoming support for Book E, and in particular the E500
core, requires support for big-endian busses because all
embedded peripherals are in the native byte-order.
With this change, there's no distinction between I/O port
space and memory mapped I/O. PowerPC doesn't have I/O port
space. Busses assign tags based on the byte-order only.
For that purpose, two global structures exist (bs_be_tag and
bs_le_tag), of which the address can be taken to get a valid
tag.
Obtained from: Juniper, Semihalf
|
| |
| |
| |
| |
| | |
support more AT91 platforms, we'll need to move this into some
platform init routine.
|
| |
| |
| |
| | |
vendor id's.
|
| |
| |
| |
| |
| |
| | |
is actually a circular log. Deal with it rolling around. Fortunately,
the log area is big and I haven't seen any roll over yet. Update and
get rid of the obsolete comment.
|
| | |
|
| |
| |
| |
| | |
45 seconds, not 15.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When system ticks are positive, for entries in the cache
bucket, syncache_timer() ran on every tick (doing nothing
useful) instead of the supposed 3, 6, 12, and 24 seconds
later (when it's time to retransmit SYN,ACK).
When ticks are negative, syncache_timer() was scheduled
for the too far future (up to ~25 days on systems with
HZ=1000), no SYN,ACK retransmits were attempted at all,
and syncache entries added in that period that correspond
to non-established connections stay there forever.
Only HEAD and RELENG_7 are affected.
Reviewed by: silby, kmacy (earlier version)
Submitted by: Maxim Dounin, ru
|
| |
| |
| |
| | |
MFC After: 3 days
|
| | |
|
| |
| |
| |
| | |
cross-device moves.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Noticed by: Andrey Chernov
|