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: Dorian Cruveiller <doriancruveiller@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>
Subject: linux-next: Signed-off-by missing for commit in the bluetooth tree
Date: Fri, 14 Feb 2025 09:07:27 +1100	[thread overview]
Message-ID: <20250214090727.518fd7a5@canb.auug.org.au> (raw)

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

Hi all,

Commit

  289a0dc9d7f9 ("Bluetooth: btusb: Add new VID/PID for WCN785x")

is missing a Signed-off-by from its author.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-02-13 22:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 22:07 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-26 21:13 linux-next: Signed-off-by missing for commit in the bluetooth tree Stephen Rothwell
2025-03-18 20:57 Stephen Rothwell
2025-01-21 20:50 Stephen Rothwell
2024-07-15  2:21 Stephen Rothwell
2024-07-10 21:55 Stephen Rothwell
2024-06-30 23:20 Stephen Rothwell
2024-04-30 21:54 Stephen Rothwell
2023-07-05 23:10 Stephen Rothwell
2022-09-20 22:30 Stephen Rothwell
2022-09-05 21:54 Stephen Rothwell
2022-07-24 21:57 Stephen Rothwell
2022-07-24 22:17 ` Stephen Rothwell
2021-04-08  0:00 Stephen Rothwell
2021-01-26  8:54 Stephen Rothwell
2021-01-26  9:46 ` Bastien Nocera
2020-04-28 22:09 Stephen Rothwell
2017-12-29 23:25 Stephen Rothwell
2017-12-29 23:32 ` Stephen Rothwell
2017-12-30  7:44   ` Johan Hedberg
2017-12-31 11:32     ` Andy Shevchenko

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=20250214090727.518fd7a5@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=doriancruveiller@gmail$(echo .)com \
    --cc=johan.hedberg@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=luiz.von.dentz@intel$(echo .)com \
    --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