wd33c93: split wd33c93_timeout() into timeout and callback
The code actually directly calls the same function for both
processing a timeout (and thus sending an abort, bus reset, etc)
and the callout running.
However, the timeout code doesn't actually complete an acb.
So if an acb times out, it seems to just .. be timed out.
Forever.
So in preparation for adding support for completing an acb with
timeout, split wd33c93_timeout() into timeout and callout.
This should be a no-op.
Patch from Adrian Chadd on port-mips@:
https://mail-index.netbsd.org/port-mips/2025/12/01/msg001535.html
wd33c93: add a debug section for submitted SCSI requests from scsipi
Whilst debugging things like hangs I found it useful to know the
class of scsi request coming in from the upper layer.
* Add a new debug bit entry - SCSIREQ
* Use it to echo the submitted SCSI requests
* Note that the unhandled one will just .. never be serviced, which is
problematic and should be addressed in a subsequent commit.
Patch from Adrian Chadd on port-mips@:
https://mail-index.netbsd.org/port-mips/2025/12/01/msg001535.html
wd33c93: abort the given transfer, not what's on or not currently active
The timeout is per-transfer, not global. And if this happens after
a state changing event - eg the device disconnecting - then sc->sc_nexus
is NULL. Calling wd33c93_abort() with a NULL acb leads to a panic.
Patch from Adrian Chadd on port-mips@:
https://mail-index.netbsd.org/port-mips/2025/12/01/msg001535.html
[MLIR][Python] Rename `GreedyRewriteDriverConfig` to `GreedyRewriteConfig` (#175409)
This is mainly for two purposes:
1. to keep it consistent with the C++ class name
`mlir::GreedyRewriteConfig`,
2. to make it shorter.
Since this type was only added a few days ago
(654b3e844f21d3f64521e9cb028efdfebbf99bb4), it shouldn’t cause any
obvious compatibility issues.
ruby-nokogiri: update to 1.19.0
Upstream changes:
https://github.com/sparklemotion/nokogiri/releases/tag/v1.19.0
v1.19.0 / 2025-12-28
Ruby
This release is focused on changes to Ruby version support,
and is otherwise functionally identical to v1.18.10.
* Introduce native gem support for Ruby 4.0. #3590
* End support for Ruby 3.1, for which upstream support ended 2025-03-26.
* End support for JRuby 9.4 (which targets Ruby 3.1 compatibility).
py-pdf: update to 6.6.0.
## Version 6.6.0, 2026-01-09
### Security (SEC)
- Improve handling of partially broken PDF files (#3594)
### Deprecations (DEP)
- Block common page content modifications when assigned to reader (#3582)
### New Features (ENH)
- Embellishments to generated text appearance streams (#3571)
### Bug Fixes (BUG)
- Do not consider multi-byte BOM-like sequences as BOMs (#3589)
### Robustness (ROB)
- Avoid empty FlateDecode outputs without warning (#3579)
[8 lines not shown]
[mlir][Python] fix dialect extensions which bind C types (#175405)
Fix some dialect bindings I missed in https://github.com/llvm/llvm-project/pull/174156 so they don't bind C structs (because that leads to multiple registration in the case when multiple packages are used simultaneously).
