From: Keith Busch <kbusch@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <axboe@kernel.dk>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Busch <keith.busch@intel.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the block tree
Date: Thu, 23 May 2019 15:52:07 -0600 [thread overview]
Message-ID: <20190523215206.GA15192@localhost.localdomain> (raw)
In-Reply-To: <20190524074500.1fde68d6@canb.auug.org.au>
On Fri, May 24, 2019 at 07:45:00AM +1000, Stephen Rothwell wrote:
> Commits
>
> 5fb4aac756ac ("nvme: release namespace SRCU protection before performing controller ioctls")
> 90ec611adcf2 ("nvme: merge nvme_ns_ioctl into nvme_ioctl")
> 3f98bcc58cd5 ("nvme: remove the ifdef around nvme_nvm_ioctl")
> 100c815cbd56 ("nvme: fix srcu locking on error return in nvme_get_ns_from_disk")
>
> are missing a Signed-off-by from their committer.
Oops, I'd only added my Reviewed-by. Do I need to update the commit
messages and resend, or is this just putting me on notice for next time?
next prev parent reply other threads:[~2019-05-23 21:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 21:45 linux-next: Signed-off-by missing for commits in the block tree Stephen Rothwell
2019-05-23 21:52 ` Keith Busch [this message]
2019-05-23 22:33 ` Stephen Rothwell
2019-05-23 22:54 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 22:21 Stephen Rothwell
2025-12-04 22:44 ` Jens Axboe
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-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=20190523215206.GA15192@localhost.localdomain \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--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.