All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Missing signoff in the bluetooth tree
Date: Fri, 4 Sep 2026 17:07:01 +0100	[thread overview]
Message-ID: <aprspVnTJDpAp7O3@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

Commits

  71729d60938f4 ("Bluetooth: btusb: Fix leaked runtime PM reference in btusb_reset")
  a78f54e23804a ("Bluetooth: btusb: mediatek: Fix leaked runtime PM reference in reset")
  b3850074b2c49 ("Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev")
  1cdf710cc2a13 ("Bluetooth: btintel_pcie: remove duplicate BTINTEL_PCIE_MAGIC_NUM definition")
  21c3501e5f464 ("Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()")
  860043e482746 ("Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware")
  9aa9447804c7b ("Bluetooth: btbcm: Add Synaptics 4384 chip support")
  29d82dcf72731 ("Bluetooth: dt-bindings: net: bluetooth: add BCM4384")

are missing a Signed-off-by from their committers

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-09-04 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 16:07 Mark Brown [this message]
2026-09-07 23:05 ` Missing signoff in the bluetooth tree Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-09-11 13:21 Mark Brown
2026-09-07 11:01 Mark Brown
2026-09-07 23:06 ` Mark Brown
2026-05-28 12:03 Mark Brown
2026-06-01 18:17 ` Mark Brown
2026-06-08 15:11   ` Mark Brown
2026-05-26 21:16 Mark Brown

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=aprspVnTJDpAp7O3@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.