Cool. I'll also tweak wg_peer_create() in DragonFly to propagate the error. Thank you.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 19 2025
May 26 2025
Apr 16 2025
Apr 12 2025
In D49796#1135140, @kevans wrote:Replaces D46670; I've set the author to this one to Aaron as I've only made two very minor tweaks from what appears in DragonflyBSD:
Apr 3 2025
Hi, I just synced the changes from DragonFly BSD and opened the PR at https://github.com/freebsd/freebsd-src/pull/1635.
Mar 30 2025
In D49576#1130271, @kib wrote:Did you observed the double unlock on the real system? I am asking because I suspect that the patch is based on local code reading only.
Mar 19 2025
Well, you cannot just declare timeout(1) is compliant with (or even is expected to conform to) the POSIX.1-2024 Standard without actually updating it.
Actually, the current version has several behaviors (e.g., signal catching, signal propagation) that don't comply with the Standard.
Sep 16 2024
Hi. Sorry for my delayed reply.
May 5 2023
Hi, I managed to find the 00781ca1-5de3-405f-abb8-379c3c076984 GUID should be AMI_ROM_LAYOUT_GUID.
For example, see https://github.com/raywu-aaeon/Ryzen2000_4000/blob/fe2d3445fcac24e7554c4d2d78d236bbaf1a28b8/AmiModulePkg/AmiModulePkg.dec#L374 .
Dec 20 2020
In D27415#617272, @dch wrote:Bump for ZT 1.6.2, waiting on DFLYBSD update
Jun 26 2020
Minor cleanup suggestion.
Jun 4 2020
Cool. I've tested this change and it works fine on DragonFly BSD. Thank you for the help.