From: Christoph Hellwig <hch@lst.de>
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>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Arnav Dawn" <a.dawn@samsung.com>,
"Guan Junxiong" <guanjunxiong@huawei.com>,
"Max Gurtovoy" <maxg@mellanox.com>,
"James Smart" <james.smart@broadcom.com>,
"Martin Wilck" <mwilck@suse.com>,
"Jan H. Schönherr" <jschoenh@amazon.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Philipp Reisner" <philipp.reisner@linbit.com>,
"Lars Ellenberg" <lars.ellenberg@linbit.com>,
"Roland Kammerer" <roland.kammerer@linbit.com>
Subject: Re: linux-next: Signed-off-bys missing for commits in the block tree
Date: Wed, 30 Aug 2017 19:09:36 +0200 [thread overview]
Message-ID: <20170830170936.GA3925@lst.de> (raw)
In-Reply-To: <20170831030647.19c22478@canb.auug.org.au>
On Thu, Aug 31, 2017 at 03:06:47AM +1000, Stephen Rothwell wrote:
> Commits
>
> b6dccf7fae43 ("nvme: add support for FW activation without reset")
> 62346eaeb2f1 ("nvme: define NVME_NSID_ALL")
> 9b483da15dd0 ("nvme-fabrics: log a warning if hostid is invalid")
> ad4e05b24c42 ("nvme: add symbolic constants for CC identifiers")
> 60b43f627a71 ("nvme: rename AMS symbolic constants to fit specification")
> 5533d42480d6 ("nvme-fc: Reattach to localports on re-registration")
> 48fa362b6c3f ("nvmet-fc: simplify sg list handling")
> 01f33c336e2d ("string.h: add memcpy_and_pad()")
> 17c39d053a46 ("nvmet: use memcpy_and_pad for identify sn/fr")
> a7b7c7a105a5 ("nvme-rdma: Use unlikely macro in the fast path")
> 5228b3280b9b ("nvme: fix uninitialized prp2 value on small transfers")
> 07fbd32a6b21 ("nvme: honor RTD3 Entry Latency for shutdowns")
>
> are missing a Signed-off-bys from their committers.
They all have singnoffs from the original committer. It's just
that we team-maintain the tree and had a rebase.
Are we supposed to add another Signoff just for the rebase?
next prev parent reply other threads:[~2017-08-30 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:06 linux-next: Signed-off-bys missing for commits in the block tree Stephen Rothwell
2017-08-30 17:09 ` Christoph Hellwig [this message]
2017-08-30 17:34 ` Stephen Rothwell
2017-08-30 17:34 ` Stephen Rothwell
2017-08-30 18:13 ` Christoph Hellwig
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=20170830170936.GA3925@lst.de \
--to=hch@lst.de \
--cc=a.dawn@samsung.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=guanjunxiong@huawei.com \
--cc=james.smart@broadcom.com \
--cc=jschoenh@amazon.de \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=maxg@mellanox.com \
--cc=mwilck@suse.com \
--cc=philipp.reisner@linbit.com \
--cc=roland.kammerer@linbit.com \
--cc=sagi@grimberg.me \
--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.