From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: Ismael Ferreras Morezuelas <swyterzone@gmail.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the bluetooth tree
Date: Thu, 10 Nov 2022 04:39:26 +1100 [thread overview]
Message-ID: <20221110043926.66f76057@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hi all,
In commit
14026a4ed275 ("Bluetooth: btusb: Fix CSR clones again by re-adding ERR_DATA_REPORTING quirk")
Fixes tags
Fixes: 63b1a7dd3 (Bluetooth: hci_sync: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING)
Fixes: e168f69008 (Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR)
Fixes: 766ae2422b (Bluetooth: hci_sync: Check LMP feature bit instead of quirk)
have this problem:
- SHA1 should be at least 12 digits long
This can be fixed for the future by setting core.abbrev to 12 (or
more) or (for git v2.11 or later) just making sure it is not set
(or set to "auto").
Also, please keep all the commit message tags together at the end of
the commit message.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-09 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:39 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-30 21:50 linux-next: Fixes tag needs some work in the bluetooth tree Stephen Rothwell
2024-04-30 22:24 ` Sungwoo Kim
2022-08-31 23:35 Stephen Rothwell
2022-07-24 21:53 Stephen Rothwell
2022-07-24 21:59 ` Stephen Rothwell
2022-07-12 22:48 Stephen Rothwell
2022-01-06 21:19 Stephen Rothwell
2021-05-08 2:13 Stephen Rothwell
2020-10-01 11:53 Stephen Rothwell
2020-10-01 19:39 ` Anant Thazhemadam
2020-07-28 12:24 Stephen Rothwell
2020-05-29 12:14 Stephen Rothwell
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=20221110043926.66f76057@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hdegoede@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=swyterzone@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).