From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.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 block tree
Date: Mon, 9 Jun 2025 06:13:06 +0200 [thread overview]
Message-ID: <20250609041306.GA26287@lst.de> (raw)
In-Reply-To: <aEISwo8LR8hG0zyV@kbusch-mbp>
On Thu, Jun 05, 2025 at 03:57:22PM -0600, Keith Busch wrote:
> On Fri, Jun 06, 2025 at 07:52:30AM +1000, Stephen Rothwell wrote:
> > Commit
> >
> > 10f4a7cd724e ("nvme: fix command limits status code")
> >
> > is missing a Signed-off-by from its author.
>
> FWIW, my Signed-off-by is in the original posting, so it must have
> accidently been chopped off somewhere on the way.
>
> https://lore.kernel.org/linux-nvme/20250520202037.2751433-1-kbusch@meta.com/
I guess that was me when editing it to make the commit log more
detailed, sorry.
next prev parent reply other threads:[~2025-06-09 4:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 21:52 linux-next: Signed-off-by missing for commit in the block tree Stephen Rothwell
2025-06-05 21:55 ` Jens Axboe
2025-06-05 22:00 ` Keith Busch
2025-06-05 21:57 ` Keith Busch
2025-06-05 22:04 ` Jens Axboe
2025-06-09 4:13 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-18 21:48 Stephen Rothwell
2025-11-18 21:59 ` Jens Axboe
2025-01-12 20:51 Stephen Rothwell
2025-01-12 22:00 ` Jens Axboe
2024-09-09 22:06 Stephen Rothwell
2024-09-09 22:12 ` Jens Axboe
2024-09-08 22:03 Stephen Rothwell
2023-01-22 21:08 Stephen Rothwell
2023-01-22 21:30 ` Jens Axboe
2023-01-22 21:34 ` Stephen Rothwell
2023-01-22 21:37 ` Jens Axboe
2022-07-20 13:16 Stephen Rothwell
2022-07-20 13:21 ` Christoph Hellwig
2022-07-20 15:58 ` Jens Axboe
2022-03-29 21:11 Stephen Rothwell
2022-03-30 5:00 ` Christoph Hellwig
2021-08-10 21:58 Stephen Rothwell
2021-06-08 22:31 Stephen Rothwell
2021-04-11 22:34 Stephen Rothwell
2021-04-12 2:14 ` Jens Axboe
2021-04-12 2:26 ` Sowjanya Komatineni
2021-04-12 2:36 ` Jens Axboe
2021-03-18 23:16 Stephen Rothwell
2021-03-18 23:25 ` Jens Axboe
2021-03-19 8:02 ` Stefan Metzmacher
2021-03-19 13:08 ` Jens Axboe
2021-03-19 13:10 ` Stefan Metzmacher
2021-03-04 23:54 Stephen Rothwell
2021-01-25 9:43 Stephen Rothwell
2021-01-25 15:18 ` Jens Axboe
2020-12-02 20:52 Stephen Rothwell
2020-06-26 23:08 Stephen Rothwell
2020-04-08 21:59 Stephen Rothwell
2019-05-22 21:50 Stephen Rothwell
2019-05-22 23:26 ` Jens Axboe
2018-12-16 6:26 Stephen Rothwell
2018-12-16 10:18 ` Christoph Hellwig
2018-12-16 15:33 ` Jens Axboe
2018-08-05 21:51 Stephen Rothwell
2018-08-06 1:16 ` Jens Axboe
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=20250609041306.GA26287@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.