All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anant Thazhemadam <anant.thazhemadam@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the bluetooth tree
Date: Fri, 2 Oct 2020 01:09:25 +0530	[thread overview]
Message-ID: <bb4e90b0-9fea-4160-cb29-0a2bb247e475@gmail.com> (raw)
In-Reply-To: <20201001215350.02b20b8b@canb.auug.org.au>


On 01/10/20 5:23 pm, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
>   44d59235ace5 ("Bluetooth: hci_h5: close serdev device and free hu in h5_close")
>
> Fixes tag
>
>   Fixes: https://syzkaller.appspot.com/bug?extid=6ce141c55b2f7aafd1c4
>
> has these problem(s):
>
>   - No SHA1 recognised
>
> Fixes tags normally refer to the commit that is fixed.
>
I'm sorry for that.

The commit that was fixed is
    ce945552fde4 (Bluetooth: hci_h5: Add support for serdev enumerated devices)

I'll send in a v2 soon fixing the tag.

Thanks,
Anant


  reply	other threads:[~2020-10-01 19:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 11:53 linux-next: Fixes tag needs some work in the bluetooth tree Stephen Rothwell
2020-10-01 19:39 ` Anant Thazhemadam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30 21:50 Stephen Rothwell
2024-04-30 22:24 ` Sungwoo Kim
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-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=bb4e90b0-9fea-4160-cb29-0a2bb247e475@gmail.com \
    --to=anant.thazhemadam@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.