From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, Dominique Martinet <asmadeus@codewreck.org>,
Jeff Layton <jlayton@kernel.org>,
Marc Dionne <marc.dionne@auristor.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
v9fs-developer@lists.sourceforge.net,
linux-afs@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] fscache, 9p, afs, nfs: Fix kerneldoc warnings and one unused variable
Date: Tue, 05 Oct 2021 14:34:39 +0100 [thread overview]
Message-ID: <1082805.1633440879@warthog.procyon.org.uk> (raw)
Hi Linus,
Could you consider pulling these changes please?
The first four patches fix kerneldoc warnings in fscache, afs, 9p and nfs -
they're mostly just comment changes, though there's one place in 9p where a
comment got detached from the function it was attached to (v9fs_fid_add)
and has to switch places with a function that got inserted between
(__add_fid).
The patch on the end removes an unused symbol in fscache - I moved it last
so you can discard it if you'd rather not pull that one just now.
David
Link: https://lore.kernel.org/r/163214005516.2945267.7000234432243167892.stgit@warthog.procyon.org.uk/ # rfc v1
Link: https://lore.kernel.org/r/163281899704.2790286.9177774252843775348.stgit@warthog.procyon.org.uk/ # rfc v2
Link: https://lore.kernel.org/r/163342376338.876192.10313278824682848704.stgit@warthog.procyon.org.uk/ # split up
---
The following changes since commit 9e1ff307c779ce1f0f810c7ecce3d95bbae40896:
Linux 5.15-rc4 (2021-10-03 14:08:47 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/warning-fixes-20211005
for you to fetch changes up to ef31499a87cf842bdf6719f44473d93e99d09fe2:
fscache: Remove an unused static variable (2021-10-04 22:13:12 +0100)
----------------------------------------------------------------
Warning fixes
----------------------------------------------------------------
David Howells (5):
nfs: Fix kerneldoc warning shown up by W=1
afs: Fix kerneldoc warning shown up by W=1
9p: Fix a bunch of kerneldoc warnings shown up by W=1
fscache: Fix some kerneldoc warnings shown up by W=1
fscache: Remove an unused static variable
fs/9p/cache.c | 8 ++++----
fs/9p/fid.c | 14 +++++++-------
fs/9p/v9fs.c | 8 +++-----
fs/9p/vfs_addr.c | 14 +++++++++-----
fs/9p/vfs_file.c | 33 ++++++++++++---------------------
fs/9p/vfs_inode.c | 24 ++++++++++++++++--------
fs/9p/vfs_inode_dotl.c | 11 +++++++++--
fs/afs/dir_silly.c | 4 ++--
fs/fscache/object.c | 2 +-
fs/fscache/operation.c | 3 +++
fs/nfs_common/grace.c | 1 -
11 files changed, 66 insertions(+), 56 deletions(-)
next reply other threads:[~2021-10-05 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 13:34 David Howells [this message]
2021-10-05 17:56 ` pr-tracker-bot
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=1082805.1633440879@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=asmadeus@codewreck.org \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=mchehab@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@hammerspace.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®