| Age | Commit message (Collapse) | Author |
|---|
|
|
|
JH7100 SoC.
ok jsg@
|
|
for the lock operation and to pass a value to the unlock operation.
sofree() still needs an extra flag to know if sounlock() should be called
or not. But sofree() is called less often and mostly without keeping the lock.
OK mpi@ mvs@
|
|
Fix a whitespace issue.
|
|
Apparently 60 * 5 + 4 seconds is 5 minutes. Presumably this is the case
with sufficiently potent crack, which would explain a few things in here.
|
|
The fallback to SHA-1 if SHA-256 is disabled fell victim to tedu many
moons ago when this file was still called s3_clnt.c and had no RCS ID.
|
|
improved diagnostics for the \C escape sequence
|
|
The restriction of only allowing ' as the delimiter was introduced
by kristaps@ on 2011/04/09 when he first supported \C.
For most other escape sequences, similar restrictions were relaxed
later on, but for the rarely used \C, it was apparently forgotten.
While here, reject empty character names: they are never valid.
|
|
(in particular the dwmmc(4) and dwge(4) devices; there may be more).
ok jsg@
|
|
controller. There are various incarnations of the controller. This diff
only adds support for the "V1"/"CDNS3" version as found on the StarFive
JH7100 SoC. Further changes may be needed to support controllers integrated
on other SoCs.
ok jsg@
|
|
|
|
errors several times (for instance, if a file doesn't exist, its checksum
is not going to match, obviously)
|
|
don't do it again (would skew the file system usage a bit).
Also: we don't need to check for firmware if we're not actively deleting.
normal updates won't touch them.
|
|
the code that calls delete_handle already
|
|
several hundred copies of the same file (even thousands! I'm looking at you
sdcc), so matching through a list is O(n^2).
So hash the hashes on the actual file name so that we match directly if
the same name file didn't change, and use the first entry otherwise, since
the name won't match.
speeds up updating of texlive somewhat, and makes a huge difference for sdcc.
|
|
|
|
From Gustavo A. R. Silva
195fffbf8291a84580762ac6e3101489954d0216 in linux 5.15.y/5.15.45
336feb502a715909a8136eb6a62a83d7268a353b in mainline linux
|
|
|
|
|
|
|
|
From Alex Deucher
62e9bd20035b53ff6c679499c08546d96c6c60a7 in mainline linux
|
|
|
|
|
|
diagnostics. Distinguish "incomplete escape sequence", "invalid special
character", and "unknown special character" from the generic "invalid
escape sequence", also promoting them from WARNING to ERROR because
incomplete escape sequences are severe syntax violations and because
encountering an invalid or unknown special character makes it likely
that part of the document content intended by the authors gets lost.
|
|
|
|
Instead of passing it around all the time put the fib_priority into the
kroute state. It is only needed in send_rtmsg() in the end.
Additionally insert F_BGP_INSERTED routes with a special RTP_MINE priority.
This makes changing the fib_priority at runtime simpler because there
is no need to alter the kroute table anymore.
OK tb@ deraadt@
|
|
call mandoc_msg() only once at the end, not sometimes in the middle,
classify incomplete, non-expanding escape sequences as ESCAPE_ERROR,
and also reduce the number of return statemants;
no formatting change intended.
|
|
mvneta only supports coalescing tx completions by count, so this
uses the txmit value or half the ring as the threshold, whichever
is lower.
rx coalescing has a threshold on the number of packets, and a max
time it will wait before interrupting. however, it also has a
threshold for how many spare/empty descriptors there are on the
ring too. we use this latter threshold to have the chip interrupt
as soon as it uses the allocation that the rx ring moderation has
granted, and then first two to otherwise rate limit rx to about 4k
interrupts per second.
ok patrick@
|
|
unbreaks the build on bigendian archs.
found by deraadt@
|
|
mvneta does interrupt coalescing based on time as counted by these
clocks, so being able to ask how fast they tick is useful.
lots of help and ok kettenis@
|
|
Problem reported by Chris Narkiewicz who owns such a device.
Johannes Berg provided helpful hints regarding the reason for
the firmware error seen by Chris.
|
|
changes, and be more specific about @digital-signature and @signer, since
we only use the one scheme now.
|
|
Found by anton with tlsfuzzer
ok anton
|
|
named buffers. GitHub issue 3212 from David le Blanc.
|
|
on a Star Labs StarLite Mk IV laptop the audio device is subclass audio
not hd audio, so azalia does not match
reported and tested by Chris Narkiewicz
ok deraadt@
|
|
|
|
|
|
Allocated string erroneously marked DONTFREE. From Miguel Pineiro Jr.
|
|
entry in ARGV (since circa 1989). From Miguel Pineiro Jr.
|
|
since the files array was first initialized with stdin, stdout, and
stderr (circa 1992). From Miguel Pineiro Jr.
|
|
ok jsing
|
|
ok jsing
|
|
This will be used to indicate client side support for DHE key
establishment.
ok jsing
|
|
key exchange mode extension, as required by RFC 8446, 4.2.9.
ok jsing
|
|
This way we don't crash in tls_config_insecure_noverify_cert().
From Mateusz Piotrowski on bugs
ok claudio
|
|
ok jsing
|
|
|
|
in the same way as groff:
* \\ is always reduced to \
* \. is always reduced to .
* other undefined escape sequences are usually reduced to the escape name,
for example \G to G, except during the expansion of expanding escape
sequences having the standard argument form (in particular \* and \n),
in which case the backslash is preserved literally.
Yes, this is confusing indeed.
For example, the following have the same meaning:
* .ds \. and .ds . which is not the same as .ds \\.
* \*[\.] and \*[.] which is not the same as \*[\\.]
* .ds \G and .ds G which is not the same as .ds \\G
* \*[\G] and \*[\\G] which is not the same as \*[G] <- sic!
To feel less dirty, have a leaning toothpick, if you are so inclined.
This patch also slightly improves the string shown by the "escaped
character not allowed in a name" error message.
|
|
some of them are 16 bit, so check frequently.
now i can see what packets my apu1 is dropping in hardware.
ok claudio@
|
|
|
