From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the fscache tree
Date: Sat, 11 Jun 2022 18:36:42 +1000 [thread overview]
Message-ID: <20220611183642.0a519e07@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 190 bytes --]
Hi all,
Commit
d3b63ddec3f8 ("netfs: Further cleanups after struct netfs_inode wrapper introduced")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-06-11 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 8:36 Stephen Rothwell [this message]
2022-06-11 8:47 ` linux-next: Signed-off-by missing for commit in the fscache tree David Howells
-- strict thread matches above, loose matches on Subject: below --
2022-03-06 20:18 Stephen Rothwell
2022-03-07 9:38 ` David Howells
2021-11-29 20:44 Stephen Rothwell
2021-11-29 21:47 ` David Howells
2021-01-26 11:40 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=20220611183642.0a519e07@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 \
--cc=torvalds@linux-foundation.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).