From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Busch <kbusch@kernel.org>, Max Gurtovoy <maxg@mellanox.com>,
Israel Rukshin <israelr@mellanox.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: linux-next: Signed-off-by missing for commits in the block tree
Date: Thu, 26 Mar 2020 10:34:36 +1100 [thread overview]
Message-ID: <20200326103436.0fd71727@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Hi all,
Commits
c363f249e7e6 ("nvmet-rdma: allocate RW ctxs according to mdts")
ec6d20e16c2d ("nvmet-rdma: Implement get_mdts controller op")
02cb00e233ad ("nvmet: Add get_mdts op for controllers")
2db24e4a22bc ("nvme-pci: properly print controller address")
e2a366a4b0fe ("nvme-pci: slimmer CQ head update")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-25 23:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 23:34 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20200326103436.0fd71727@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adobriyan@gmail.com \
--cc=axboe@kernel.dk \
--cc=israelr@mellanox.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxg@mellanox.com \
/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.