From: Sungwoo Kim <iam@sung-woo.kim>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
sfr@canb.auug.org.au
Subject: Re: linux-next: Fixes tag needs some work in the bluetooth tree
Date: Tue, 30 Apr 2024 18:24:35 -0400 [thread overview]
Message-ID: <CAJNyHp+-Hb29VE2-DLb1Vo51rwhJrYmN9J5_mxocFUf8Y72Vww@mail.gmail.com> (raw)
In-Reply-To: <20240501075038.2d07189b@canb.auug.org.au>
Hi, sorry for the wrong fixed tag.
On Tue, Apr 30, 2024 at 5:50 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 91708e8a4376 ("Bluetooth: msft: fix slab-use-after-free in msft_do_close()")
>
> Fixes tag
>
> Fixes: 9e14606d8f38 ("Bluetooth: disable advertisement filters during suspend")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> Maybe you meant
>
> Fixes: bf6a4e30ffbd ("Bluetooth: disable advertisement filters during suspend")
>
> or
>
> Fixes: 9e14606d8f38 ("Bluetooth: msft: Extended monitor tracking by address filter")
The correct tag is:
Fixes: 5031ffcc79b8 ("Bluetooth: Keep MSFT ext info throughout a
hci_dev's life cycle")
Would you like me to send a new patch to fix this?
Thanks,
Sungwoo.
next prev parent reply other threads:[~2024-04-30 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-09 17:39 Stephen Rothwell
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=CAJNyHp+-Hb29VE2-DLb1Vo51rwhJrYmN9J5_mxocFUf8Y72Vww@mail.gmail.com \
--to=iam@sung-woo.kim \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=sfr@canb.auug.org.au \
/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).