From: Jens Axboe <axboe@kernel•dk>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Keith Busch <kbusch@kernel•org>,
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 commits in the block tree
Date: Thu, 4 Dec 2025 15:44:49 -0700 [thread overview]
Message-ID: <a699a3aa-50b8-4258-ba71-d28c6abc9f7c@kernel.dk> (raw)
In-Reply-To: <20251205092150.0e64adb3@canb.auug.org.au>
On 12/4/25 3:21 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> d3132d5a1720 ("nvmet-fc: use pr_* print macros instead of dev_*")
> facf78e89270 ("nvmet-fcloop: remove unused lsdir member.")
> d4a3dc77e6d6 ("nvmet-fcloop: check all request and response have been processed")
> 92ee1738dd50 ("nvme-fc: check all request and response have been processed")
>
> are missing a Signed-off-by from their committer.
Oops yes - keith is redoing it, I'll re-pull when that's done.
--
Jens Axboe
next prev parent reply other threads:[~2025-12-04 22:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 22:21 linux-next: Signed-off-by missing for commits in the block tree Stephen Rothwell
2025-12-04 22:44 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-18 20:48 Stephen Rothwell
2021-10-18 20:49 ` Jens Axboe
2021-08-29 21:52 Stephen Rothwell
2021-08-29 22:11 ` Jens Axboe
2021-03-04 21:19 Stephen Rothwell
2021-03-04 22:47 ` Jens Axboe
2020-09-24 22:40 Stephen Rothwell
2020-09-24 23:05 ` Jens Axboe
2020-09-24 23:06 ` Song Liu
2020-03-25 23:34 Stephen Rothwell
2019-05-23 21:45 Stephen Rothwell
2019-05-23 21:52 ` Keith Busch
2019-05-23 22:33 ` Stephen Rothwell
2019-05-23 22:54 ` Jens Axboe
2019-04-01 18:08 Stephen Rothwell
2019-04-01 18:10 ` Jens Axboe
2018-05-26 3:50 Stephen Rothwell
2018-05-26 4:03 ` 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=a699a3aa-50b8-4258-ba71-d28c6abc9f7c@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=kbusch@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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