From: Bastien Nocera <hadess@hadess•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Marcel Holtmann <marcel@holtmann•org>,
Johan Hedberg <johan.hedberg@gmail•com>
Cc: Florian Dollinger <dollinger.florian@gmx•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the bluetooth tree
Date: Tue, 26 Jan 2021 10:46:08 +0100 [thread overview]
Message-ID: <b92aca941b344ce4552b9e4d25d4f438aff4e6d5.camel@hadess.net> (raw)
In-Reply-To: <20210126195441.69c45ad9@canb.auug.org.au>
On Tue, 2021-01-26 at 19:54 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 98d2c3e17310 ("Bluetooth: L2CAP: Try harder to accept device not
> knowing options")
>
> is missing a Signed-off-by from its author.
Marcel, is it possible to amend this to add my Signed-off-by?
Signed-off-by: Bastien Nocera <hadess@hadess•net>
Cheers
next prev parent reply other threads:[~2021-01-26 9:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:54 linux-next: Signed-off-by missing for commit in the bluetooth tree Stephen Rothwell
2021-01-26 9:46 ` Bastien Nocera [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-26 21:13 Stephen Rothwell
2025-03-18 20:57 Stephen Rothwell
2025-02-13 22:07 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
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=b92aca941b344ce4552b9e4d25d4f438aff4e6d5.camel@hadess.net \
--to=hadess@hadess$(echo .)net \
--cc=dollinger.florian@gmx$(echo .)de \
--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 \
--cc=sfr@canb$(echo .)auug.org.au \
/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