From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olga Kornievskaia <kolga@netapp.com>,
Andy Adamson <andros@netapp.com>,
Olga Kornievskaia <olga.kornievskaia@gmail.com>
Subject: linux-next: Signed-off-by missing for commit in the nfsd tree
Date: Tue, 3 Dec 2019 07:38:15 +1100 [thread overview]
Message-ID: <20191203073815.78965ad1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
Hi all,
Commit
dd4320a29d65 ("NFSD generalize nfsd4_compound_state flag names")
is missing a Signed-off-by from its author and committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-12-02 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 20:38 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 21:15 linux-next: Signed-off-by missing for commit in the nfsd tree Stephen Rothwell
2021-05-20 22:04 Stephen Rothwell
2021-05-21 13:50 ` J. Bruce Fields
2021-05-21 13:55 ` Kornievskaia, Olga
2021-05-21 14:01 ` J. Bruce Fields
2021-05-21 14:42 ` Kornievskaia, Olga
2021-05-21 14:53 ` J. Bruce Fields
2020-11-08 21:20 Stephen Rothwell
2020-11-08 21:29 ` J. Bruce Fields
2020-11-09 9:15 ` Dan Carpenter
2019-12-21 3:10 Stephen Rothwell
2017-11-27 22:52 Stephen Rothwell
2017-11-28 1:38 ` J. Bruce Fields
2017-11-28 2:02 ` Stephen Rothwell
2017-11-09 19:51 Stephen Rothwell
2017-11-09 20:06 ` J. Bruce Fields
2017-08-24 22:48 Stephen Rothwell
2017-08-25 2:21 ` J. Bruce Fields
2017-08-25 2:37 ` J. Bruce Fields
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=20191203073815.78965ad1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andros@netapp.com \
--cc=bfields@fieldses.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olga.kornievskaia@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).