All of lore.kernel.org
 help / color / mirror / Atom feed
 messages from 2026-11-14 19:00:30 to 2026-11-14 19:43:37 UTC [more...]

[REGRESSION] rtsx_usb_sdmmc: RTS5129 (0bda:0129) no longer detects SD card
 2026-11-14 19:43 UTC  (4+ messages)

[PATCH v13 0/7] KEYS: Replace assoc_array with rhashtable
 2026-11-14 19:42 UTC  (10+ messages)
` [PATCH v13 1/7] s390/cert_store: Pin the user session keyring
` [PATCH v13 2/7] s390/cert_store: Return an owned reference from find_cs_keyring()
` [PATCH v13 3/7] s390/cert_store: Skip keys that disappeared during invalidation
` [PATCH v13 4/7] s390/cert_store: Read-lock keyring semaphore in invalidate_keyring_keys()
` [PATCH v13 5/7] KEYS: Introduce keyring_is_empty()
` [PATCH v13 6/7] KEYS: Replace assoc_array with rhashtable
` [PATCH v13 7/7] lib: Remove assoc_array

[PATCH v2 0/3] drm/vc4: Fix async page flip completion
 2026-11-14 19:40 UTC  (5+ messages)
` [PATCH v2 1/3] drm/vc4: Drop BO usecnt before releasing the old FB
` [PATCH v2 2/3] drm/vc4: Complete async page flips from an ordered workqueue
` [PATCH v2 3/3] drm/vc4: Look up the async page flip fence before committing the flip

[meta-oe][PATCH 01/13] frame: Fix build with lld without x11
 2026-11-14 19:37 UTC  (13+ messages)
` [meta-networking][PATCH 02/13] dante: Fix build with lld
` [meta-multimedia][PATCH 03/13] tremor: "
` [meta-oe][PATCH 04/13] wtmpdb: "
` [meta-oe][PATCH 05/13] libkcapi: "
` [meta-multimedia][PATCH 06/13] libdc1394: Fix build with clang
` [meta-oe][PATCH 07/13] tinymembench: Fix build with clang's integrated assembler
` [meta-oe][PATCH 08/13] wvstreams, wvdial: Build with gcc
` [meta-multimedia][PATCH 09/13] caps: "
` [meta-gnome][PATCH 10/13] ibus: Fix build without x11
` [meta-networking][PATCH 11/13] rdma-core: Do not export LFS64 wrappers in librspreload when not built
` [meta-networking][PATCH 12/13] ot-br-posix: Do not error on sign-compare with musl and clang
` [meta-oe][PATCH 13/13] fluentbit: Fix build with clang 23 on riscv64

[PATCH v3 bpf-next 00/11] bpf: fmod_ret for each function that returns errors
 2026-11-14 19:37 UTC  (3+ messages)
` [PATCH v3 bpf-next 05/11] resolve_btfids: Tag the functions that return errors

linux-next: manual merge of the bpf-next tree with the origin tree
 2026-11-14 19:36 UTC  (2+ messages)

[PATCH ath-next v4 00/11] wifi: ath12k: resolve RX link id via logical link id on WCN7850/QCC2072
 2026-11-14 19:35 UTC  (4+ messages)

[PATCH v2 0/4] tpm: Cache ACPI TPM2 start method and gate tpm_crb_ffa probe
 2026-11-14 19:34 UTC  (5+ messages)
` [PATCH v2 1/4] tpm: Cache TPM2 start method
` [PATCH v2 2/4] tpm: tpm_crb_ffa: Only probe when ACPI TPM2 uses FF-A
` [PATCH v2 3/4] tpm: tpm_tis: Use cached tpm2_acpi_start_method
` [PATCH v2 4/4] tpm: tpm_crb: "

[PATCH] drm/tests: bridge: check the bridge chain callback order
 2026-11-14 19:32 UTC 

[PATCH v2 3/3] drm/amd/display: report synced displays to PowerPlay for MCLK switch
 2026-11-14 19:30 UTC  (8+ messages)

[PATCH v2 0/3] mtd: rawnand: vf610_nfc: fix the OOB of written pages and command timeouts
 2026-11-14 19:30 UTC  (9+ messages)
` [PATCH v2 1/3] mtd: rawnand: vf610_nfc: write the OOB bytes on page writes
` [PATCH v2 2/3] mtd: rawnand: vf610_nfc: keep a timed-out command from completing the next one
` [PATCH v2 3/3] mtd: rawnand: vf610_nfc: return an error when a command times out

[PATCH] archive: remove USE_THE_REPOSITORY_VARIABLE from archival modules
 2026-11-14 19:26 UTC  (2+ messages)

[PATCH v2 1/2] vfio/pci: fall back to platform ROM when pci_map_rom() fails
 2026-11-14 19:24 UTC  (4+ messages)

[PATCH 0/2] Support for sdm660 remoteproc power domains
 2026-11-14 19:23 UTC  (3+ messages)
` [PATCH 1/2] remoteproc: qcom: change resource descriptor for sdm660 adsp
` [PATCH 2/2] remoteproc: qcom: Add sdm660 cdsp resource descriptor

[PATCH net-next v3 00/10] Deliver TLS session tags to upper-layer consumers (NFSD)
 2026-11-14 19:22 UTC  (5+ messages)
` [PATCH net-next v3 01/10] handshake: Add tags to "done" downcall
` [PATCH net-next v3 10/10] NFSD: Add allow_tags to the netlink export interface

[syzbot] [mm?] possible deadlock in dup_mmap
 2026-11-14 19:19 UTC  (2+ messages)

[PATCH] nbd: do not reinitialize a live socket lock when reclassifying
 2026-11-14 19:17 UTC  (2+ messages)

[PATCH] mm/pagewalk: document missing struct members
 2026-11-14 19:14 UTC  (2+ messages)

[PATCH v3 0/5] HID: intel-thc-hid: intel-ipts: support THC IPTS ports
 2026-11-14 19:10 UTC  (5+ messages)
` [PATCH v3 2/5] HID: intel-thc-hid: intel-ipts: receive reports
` [PATCH v3 4/5] HID: intel-thc-hid: intel-ipts: handle system sleep

[PATCH] docs: translations: pt_BR: translate gdb-kernel-debugging
 2026-11-14 19:10 UTC  (2+ messages)

[PATCH bpf-next 0/3] bpf, cgroup: Don't wait for cgroup_mutex to read or free cgroup bpf state
 2026-11-14 19:10 UTC  (2+ messages)

FAILED: patch "[PATCH] mm/filemap: don't lose a folio lock wakeup to a signal" failed to apply to 5.10-stable tree
 2026-11-14 19:09 UTC  (2+ messages)
` [PATCH 5.10.y] mm/filemap: don't lose a folio lock wakeup to a signal

[PATCH net v2 0/2] net/smc: do not reuse the DMB of a nocopy device
 2026-11-14 19:09 UTC  (6+ messages)
` [PATCH net v2 1/2] dibs: loopback: reset the client id when the owner unregisters a DMB
` [PATCH net v2 2/2] net/smc: do not reuse the DMB of a nocopy device

[PATCH] net: skmsg: fix copy cursor when coalescing clones
 2026-11-14 19:08 UTC  (2+ messages)

Hi,,,I am investigating a reproducible Bluetooth SAR initialization warning on an Intel AX201 controller in an ASUS ExpertBook B5402CBA running Gentoo Linux.,,The warning occurs during firmware initialization on both Linux 7.3.3 and 7.3.4:,,```,Bluetooth: hci0: Applying legacy Bluetooth SAR,Bluetooth: hci0: Failed to send sar ddc id:0x0137 (-22),```,,I captured the initial firmware initialization with btmon and confirmed that the controller explicitly rejects Intel DDC Config Write (0xfc8b), ID 0x0137, with HCI status 0x12.,,**Environment**,,- Hardware: Intel AX201 (USB 8087:0026),- Laptop: ASUS ExpertBook B5402CBA,- Kernel: Gentoo Linux 7.3.4-bdsm (also observed on 7.3.3-bdsm),- Bluetooth firmware: 2026.29, build 82200,- Firmware SHA1 reported by controller: 0xd3d4fa22,- CNVi TOP: 0x00080400,- CNVr TOP: 0x01300504,- Intel DDC file: intel/ibt-0040-4150.ddc (symlink to ibt-0040-0041.ddc),,**Confirmed HCI sequence**,,```,DDC ID Payload HCI status,0x0128 18 Success (0x00),0x0129 03 00 Success (0x00),0x0131 06 Success (0x00),0x0132 06 Success (0x00),0x0133 07 Success (0x00),0x0137 06 08 08 Invalid HCI Command Parameters (0x12),```,,The initial DDC configuration file contains only IDs 0x0128 and 0x0129, and both are applied successfully.,,The legacy SAR parameters come from the ACPI BRDS method at:,,```,\_SB.PC00.XHCI.RHUB.HS10,```,,The method reads the Bluetooth SAR values from the ASUS GNVS SystemMemory region. The controller initialization takes the legacy SAR path.,,In `btintel_set_legacy_sar()`, the first three SAR commands succeed. The next command, ID 0x0137 with payload `06 08 08`, is rejected. The function then returns without sending the remaining legacy SAR commands.,,**Questions**,,1. Is legacy SAR DDC ID 0x0137 with a three-byte BR/EDR payload expected to be supported by this AX201 firmware and hardware generation?,2. Are the payload values `06 08 08` valid for this command, or could the rejection indicate incompatible ACPI-provided SAR values?,3. If this rejection is expected for some Intel controllers, should `btintel` check capability or handle the unsupported command differently, while preserving the required radio power restrictions?,4. Could this result in only partial application of the platform's Bluetooth SAR settings?,,The controller finishes initialization and Bluetooth remains usable. I am not claiming that this warning causes the separate intermittent hardware error 0x0c observed on the system.,,I can provide a sanitized btmon capture, relevant DSDT/BRDS excerpts, and kernel initialization logs if useful.,,Thanks for looking into this
 2026-11-14 19:08 UTC 

[PATCH 0/5] mm,drm/i915,powerpc/spufs: vm_ops->access related fixes
 2026-11-14 19:08 UTC  (3+ messages)
` [PATCH 5/5] mm: check permissions and bounds for vm_ops->access

[PATCH bpf-next] bpf, tcx: Skip RCU synchronization when the entry was newly created
 2026-11-14 19:06 UTC  (2+ messages)

[PATCH] leds: pca9532: Propagate I2C errors
 2026-11-14 19:06 UTC  (3+ messages)
` [PATCH v4] "

[PATCH] RDMA/rxe: Do not re-execute completed local ops after a retry
 2026-11-14 19:05 UTC  (2+ messages)

[PATCH] python3-pygobject: add ptest support
 2026-11-14 19:03 UTC 

[PATCH net-next v3 0/2] nfc: s3fwrn5: Add optional pvdd-supply
 2026-11-14 19:03 UTC  (4+ messages)
` [PATCH net-next v3 2/2] nfc: s3fwrn5: i2c: Enable the pvdd supply

[GIT PULL] hwmon fixes for v7.4-rc3
 2026-11-14 19:03 UTC  (2+ messages)

[PATCH] kbuild: depmod: fallback to /boot/System.map-KERNELRELEASE
 2026-11-14 19:02 UTC  (4+ messages)

[GIT PULL] xen: branch for v7.4-rc3
 2026-11-14 19:02 UTC  (2+ messages)

[PATCH v2 00/14] security-bugs doc updates
 2026-11-14 19:00 UTC  (15+ messages)
` [PATCH v2 01/14] docs: security-bugs: reorganize the document without changing its contents
` [PATCH v2 02/14] docs: security-bugs: clarify when to Cc the security team
` [PATCH v2 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact
` [PATCH v2 04/14] docs: threat-model: clarify the case of automatically mounted file systems
` [PATCH v2 05/14] docs: security-bugs: explain how to send a fix that can be applied
` [PATCH v2 06/14] docs: security-bugs: do not send archives or binary attachments
` [PATCH v2 07/14] docs: security-bugs: first-time reporters must send a single report first
` [PATCH v2 08/14] docs: security-bugs: explain what to do when a report gets no response
` [PATCH v2 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped
` [PATCH v2 10/14] docs: security-bugs: add a section for maintainers receiving reports
` [PATCH v2 11/14] docs: security-bugs: explain why directly sent reports add extra work
` [PATCH v2 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly
` [PATCH v2 13/14] docs: submitting-patches: defer to security-bugs.rst for security fixes
` [PATCH v2 14/14] docs: netdev: drop references to the securit list in the doc

[PATCH v6 00/19] Add strprefix() and fix a bug with it
 2026-11-14 19:00 UTC  (6+ messages)
` [PATCH v6 02/19] string: Add strprefix()


This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.