From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the fsinfo tree
Date: Sun, 21 Jun 2020 08:16:34 +1000 [thread overview]
Message-ID: <20200621081634.20a3d18c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
Hi all,
Commits
dbc87e74d022 ("vfs, fsinfo: Add an RCU safe per-ns mount list")
1293806368bc ("fsinfo: Add an attribute that lists all the visible mounts in a namespace")
93737ccf05ec ("fsinfo: Add an attribute that lists all the visible mounts in a namespace")
are missing a Signed-off-by from their author and committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-06-20 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 22:16 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 0:32 linux-next: Signed-off-by missing for commits in the fsinfo tree Stephen Rothwell
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=20200621081634.20a3d18c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).