From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH -next v3 0/2] sunrpc: Fix W=1 compiler warnings
Date: Mon, 16 Oct 2023 15:09:17 +0200 [thread overview]
Message-ID: <cover.1697460614.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series fixes W=1 compiler warnings in sunrpc, related to
variables that are used only when debugging is enabled.
Changes compared to v2:
- New patch "sunrpc: Wrap read accesses to rpc_task.tk_pid",
- Add Acked-by.
Changes compared to v1:
- s/uncontionally/unconditionally/,
- Drop CONFIG_SUNRPC_DEBUG check in fs/lockd/svclock.c to fix build
failure.
Thanks for your comments!
Geert Uytterhoeven (2):
sunrpc: Wrap read accesses to rpc_task.tk_pid
sunrpc: Use no_printk() in dfprintk*() dummies
fs/lockd/svclock.c | 2 --
fs/nfs/filelayout/filelayout.c | 12 ++++++------
fs/nfs/flexfilelayout/flexfilelayout.c | 9 +++------
include/linux/sunrpc/debug.h | 6 +++---
include/linux/sunrpc/sched.h | 10 ++++++++++
net/sunrpc/clnt.c | 2 +-
net/sunrpc/debugfs.c | 2 +-
7 files changed, 24 insertions(+), 19 deletions(-)
--
2.34.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2023-10-16 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:09 Geert Uytterhoeven [this message]
2023-10-16 13:09 ` [PATCH -next v3 1/2] sunrpc: Wrap read accesses to rpc_task.tk_pid Geert Uytterhoeven
2023-10-16 21:15 ` Benjamin Coddington
2023-10-17 6:35 ` Geert Uytterhoeven
2023-10-16 13:09 ` [PATCH -next v3 2/2] sunrpc: Use no_printk() in dfprintk*() dummies Geert Uytterhoeven
2023-10-16 21:16 ` Benjamin Coddington
2023-10-19 7:56 ` Geert Uytterhoeven
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=cover.1697460614.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=tom@talpey.com \
--cc=trond.myklebust@hammerspace.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