public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Marcel Holtmann <marcel@holtmann•org>,
	Johan Hedberg <johan.hedberg@gmail•com>
Cc: Calvin Owens <calvin@wbinvd•org>,
	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: Wed, 3 Sep 2025 09:23:46 +1000	[thread overview]
Message-ID: <20250903092346.0cb5db2a@canb.auug.org.au> (raw)

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

Hi all,

In commit

  16ebf6c26de5 ("Bluetooth: Fix build after header cleanup")

Fixes tag

  Fixes: 74bcec450eea ("Bluetooth: remove duplicate h4_recv_buf() in header")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 0e272fc7e17d ("Bluetooth: remove duplicate h4_recv_buf() in header")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-09-02 23:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 23:23 Stephen Rothwell [this message]
2025-09-03 13:58 ` linux-next: Fixes tag needs some work in the bluetooth tree Calvin Owens
  -- strict thread matches above, loose matches on Subject: below --
2024-08-27 22:33 Stephen Rothwell
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-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=20250903092346.0cb5db2a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=calvin@wbinvd$(echo .)org \
    --cc=johan.hedberg@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=marcel@holtmann$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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