From: Johan Hovold <johan@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH v2 0/3] Bluetooth: btusb: fix wakeup irq devres lifetime
Date: Thu, 2 Apr 2026 11:27:01 +0200 [thread overview]
Message-ID: <20260402092704.2346710-1-johan@kernel.org> (raw)
This series fixes a wakeup source leak and a (currently benign) OOB
wakeup interrupt devres lifetime issue.
Included is also a related cleanup.
Note that these are intended for 7.1 (e.g. as the fixes are not
critical) and apply on top of linux-next which has commit 2db5a8b68e31
("Bluetooth: btusb: refactor endpoint lookup").
Johan
Changes in v2:
- fix wakeup source leak (new patch)
- fix disconnect-while-suspended issue by making interrupt non-managed
- amend devres lifetime fix commit message with a reference to changed
devres behaviour
- clean up error handling (new patch)
Johan Hovold (3):
Bluetooth: btusb: fix wakeup source leak on probe failure
Bluetooth: btusb: fix wakeup irq devres lifetime
Bluetooth: btusb: clean up probe error handling
drivers/bluetooth/btusb.c | 50 +++++++++++++++++++++++++--------------
1 file changed, 32 insertions(+), 18 deletions(-)
--
2.52.0
next reply other threads:[~2026-04-02 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 9:27 Johan Hovold [this message]
2026-04-02 9:27 ` [PATCH v2 1/3] Bluetooth: btusb: fix wakeup source leak on probe failure Johan Hovold
2026-04-02 10:17 ` Bluetooth: btusb: fix wakeup irq devres lifetime bluez.test.bot
2026-04-02 9:27 ` [PATCH v2 2/3] " Johan Hovold
2026-04-02 9:27 ` [PATCH v2 3/3] Bluetooth: btusb: clean up probe error handling Johan Hovold
2026-04-02 14:16 ` [PATCH v2 0/3] Bluetooth: btusb: fix wakeup irq devres lifetime Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260402092704.2346710-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.