- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
spit the diff as requested by maintainer
I had mistakenly uploaded the wrong diff file
Update to bvwm.6 and address feedback (fuz, jrm, adamw)
The versions of a few components I help manage are out of date now.
How are these files pulled in and how often/how are SBOMs generated? If the answer is "not that often"/"only if a command is run on demand", I would seriously encourage that we don't hardcode versions like this and instead compute them dynamically from other files which can be considered the "sources of truth", e.g., .pc files, etc.
Hopefully better comments, passed though some automatic checker.
Restore the correct diff.
Set FreeBSD's website as the default URL in SBOM files.
Detected by pccritic(1) from pkgconf 3.0.7.
Set FreeBSD's website as the default URL in SBOM files.
Detected by pccritic(1) from pkgconf 3.0.7.
No, it wasn't: aior->more stays set, so ahci_ioreq_cb() resubmits the same request forever. ahci_build_iov() now returns an error and the callers fail the command as if blockif had failed.
Free allocated fake pages.
Add some comments explaining the intent.
Avoid going through the vm_page_array[] at all, the page physical address is all that is needed for a fake page construction.
LGTM. The commit message should include *why* the change is being made though, not just *what* is being changed.
Yesterday
Implement linux_fchmodat as a wrapper for linux_fchmodat2 to reduce future
code duplication.
Add copyright statement to the man page.
Rework API.
Add man page.
Fix pre-existing race also affecting the patch.
Yet some more code style rework
I'll have to go and look; I wonder if there was a mis-merge somewhere. Due to other generic LinuxKPI changes which were in review for quite a long time I had to rebase the entire code back then to get it in and only the recent changes (which were backed out as they broke drm-kmod as we know) would actually make all the lock assertions work again on a GENERIC kernel.
In D49636#1353346, @jsm wrote:do not use system poco (we are too far behind, and the --with-system-poco usage is apparently deprecated by upstream) and avoid use of (TM) names. the LOCAL files are at people.freebsd.org/~jsm for now. Upstream change is https://gerrit.collaboraoffice.com/c/online/+/6588 but leaves still smt to the ports patches..
In D59883#1395793, @markj wrote:(Still working on testing this. If I test drm-6.12 on my laptop, I get a corrupted display with or without this patch. After retesting drm-6.6 it seems there is some recent regression in main, as I now see similar symptoms there too, so I am bisecting that instead, hopefully will figure it out soon.)
Correction to my previous comment: all five sites now use pci_nvme_status_genc() with NVME_SC_INTERNAL_DEVICE_ERROR.
Thank you for the review and the status code correction.
poudriere testport on 15.1-RELEASE amd64 & aarch64 with PostgreSQL 18.
portlint -AC clean; stage-qa and check-plist clean.