From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Howells <dhowells@redhat•com>
Cc: 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: Tue, 26 Jan 2021 22:40:49 +1100 [thread overview]
Message-ID: <20210126224049.2841074b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Hi all,
Commits
daa94e1d8977 ("NFS: Convert readpage to readahead and use netfs_readahead for fscache")
08a636bcf023 ("NFS: Convert to the netfs API and nfs_readpage to use netfs_readpage")
56ee45bd6a23 ("NFS: Allow internal use of read structs and functions")
31d24fb6dff4 ("NFS: Add nfs_pageio_complete_read() and remove nfs_readpage_async()")
9cf28394cb4a ("NFS: Call readpage_async_filler() from nfs_readpage_async()")
cdb77ce77d41 ("NFS: Refactor nfs_readpage() and nfs_readpage_async() to use nfs_readdesc")
70d842718007 ("NFS: In nfs_readpage() only increment NFSIOS_READPAGES when read succeeds")
150c02f5ba86 ("NFS: Clean up nfs_readpage() and nfs_readpages()")
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:[~2021-01-26 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:40 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-29 20:44 linux-next: Signed-off-by missing for commit in the fscache tree Stephen Rothwell
2021-11-29 21:47 ` David Howells
2022-03-06 20:18 Stephen Rothwell
2022-03-07 9:38 ` David Howells
2022-06-11 8:36 Stephen Rothwell
2022-06-11 8:47 ` David Howells
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=20210126224049.2841074b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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