From: Jens Axboe <axboe@kernel.dk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: Fri, 25 May 2018 22:03:06 -0600 [thread overview]
Message-ID: <fc204457-1e79-131b-d166-5fec6d0cc734@kernel.dk> (raw)
In-Reply-To: <20180526135004.00b19986@canb.auug.org.au>
On 5/25/18 9:50 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> Commits
>
> 287a63ebbe7c ("nvme: mark the result argument to nvme_complete_async_event volatile")
> 750dde4472e4 ("nvme-pci: simplify nvme_cqe_valid")
> d1f06f4ae041 ("nvme-pci: move ->cq_vector == -1 check outside of ->q_lock")
> 1ab0cd6966fc ("nvme-pci: split the nvme queue lock into submission and completion locks")
> 1eae349d18fc ("nvme-pci: drop IRQ disabling on submission queue lock")
>
> are missing a Signed-off-by from their committer.
Thanks for the heads up. Not a huge problem for these particular commits,
--
Jens Axboe
next prev parent reply other threads:[~2018-05-26 4:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 3:50 linux-next: Signed-off-by missing for commits in the block tree Stephen Rothwell
2018-05-26 4:03 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-01 18:08 Stephen Rothwell
2019-04-01 18:10 ` Jens Axboe
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
2020-03-25 23:34 Stephen Rothwell
2020-09-24 22:40 Stephen Rothwell
2020-09-24 23:05 ` Jens Axboe
2020-09-24 23:06 ` Song Liu
2021-03-04 21:19 Stephen Rothwell
2021-03-04 22:47 ` Jens Axboe
2021-08-29 21:52 Stephen Rothwell
2021-08-29 22:11 ` Jens Axboe
2021-10-18 20:48 Stephen Rothwell
2021-10-18 20:49 ` Jens Axboe
2025-12-04 22:21 Stephen Rothwell
2025-12-04 22:44 ` 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=fc204457-1e79-131b-d166-5fec6d0cc734@kernel.dk \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox