[ARM][GISel] Enable extended LLT (#191830)
This adds the basic enablement for extended LLT for Arm GISel. This is
relatively basic, with no direct use of fp16/bf16 yet. Most of the
changes involved updating the tests and some minor updates to handle
bitcast and merge/unmerge correctly.
Merge tag 'driver-core-7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core
Pull driver core fixes from Danilo Krummrich:
- Fix an unused-function warning in the Rust I/O code that breaks
builds with CONFIG_PCI disabled and CONFIG_WERROR enabled
- Fix kernfs sparse warnings on SMP Alpha when inheriting a parent
node's group ID
- Add Johan Hovold as an auxiliary bus maintainer
* tag 'driver-core-7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core:
MAINTAINERS: update auxiliary bus entry
kernfs: avoid READ_ONCE() on a kgid_t in kernfs_new_node()
rust: io: fix unused Flags::from_raw warning without CONFIG_PCI
[MemProf] Update edge alloc types when moving context ids to a new node (#239879)
When an inlined callsite is matched to a sequence of stack nodes, the
context ids matched to it are moved from the original edges to a new
node. The alloc types of the original edges that kept some context ids
were not updated, so an edge left with only not cold contexts could
still be marked cold. Since the ambiguous attribute handling now relies
on the alloc types after cloning, an allocation reached through such an
edge was marked ambiguous instead of not cold.
Recompute the alloc type of any edge that keeps context ids, both in
connectNewNode and for the edges between the matched stack nodes.
Assisted-by: Gemini
fts_read: fix potential double free on FCHDIR() failure
Part of the contract for fts_read() is that we must always reset
sp->fts_cur immediately before return. There was one instance where
a failed FCHDIR() was not setting sp->fts_cur to 'p' before return,
leaving sp->fts_cur pointing to a freed value.
From Acts1631
OK tb@
Merge tag 'ata-7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux
Pull ata fixes from Niklas Cassel:
- Allow re-enabling NCQ, after EH disabled it, by writing the current
queue depth to the queue_depth sysfs attribute (Igor)
- Retry failed non-NCQ commands when their sense data asks for a
retry, as is already done for NCQ commands. Previously, such
non-NCQ commands were never retried (me)
- Only check the power mode of ATA and ZAC devices before putting
them in standby mode (on suspend, shutdown or device removal).
libata never puts other devices, such as ATAPI devices, in standby
mode, and some ATAPI devices reject the CHECK POWER MODE command
(Giuseppe)
- Fix several bugs in the MODE SELECT translation.
[35 lines not shown]
Merge tag 'firewire-fixes-7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394
Pull firewire fix from Takashi Sakamoto:
"Fix a race in the 1394 OHCI driver, introduced in v7.4-rc1
Queueing an AT local request in interrupt context can race with
dequeueing requests in a workqueue without disabling interrupts,
potentially leading to a deadlock"
* tag 'firewire-fixes-7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394:
firewire: ohci: avoid potential deadlock when queueing AT local requests
TargetLowering: Take libcall info from analysis
Pass in LibcallLoweringInfo to getDefaultSafeStackPointerLocation
instead of relying on TargetLoweriing's static copy which will
eventually be removed.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
comms/py-pynitrokey: Update 0.14.0 => 0.14.1
This is a maintenance release that updates the bundled root
certificates to remove the compromised emSign certificate.
Changelog:
https://github.com/Nitrokey/pynitrokey/releases/tag/v0.14.1
PR: 299842
Approved by: osa, vvd (mentors, implicit)
MFH: 2026Q4
