From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/3] NFS: Address build error when built with W=1
Date: Fri, 27 Feb 2026 16:18:19 +0800 [thread overview]
Message-ID: <20260227-nfs-v1-0-2a6ea2ca8528@nxp.com> (raw)
I built x86_64_defconfig with COMPILE_TEST=y and W=1, then saw
three build errors from fs/nfs: "error: variable set but not used"
Detailed info could be found in each patch commit log.
With the patchset, kernel build pass.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (3):
NFS: flexfilelayout: return ERR_PTR from nfs4_ff_alloc_deviceid_node() and fix caller
NFS: flexfilelayout: Mark err as __maybe_unused in ff_layout_io_track_ds_error
NFS: nfs4proc: Mark ptr as __maybe_unused in nfs4_proc_create_session
fs/nfs/flexfilelayout/flexfilelayout.c | 4 ++--
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 2 +-
fs/nfs/nfs4proc.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
---
base-commit: 7d6661873f6b54c75195780a40d66bad3d482d8f
change-id: 20260227-nfs-ff0f0f96fea3
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2026-02-27 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 8:18 Peng Fan (OSS) [this message]
2026-02-27 8:18 ` [PATCH 1/3] NFS: flexfilelayout: return ERR_PTR from nfs4_ff_alloc_deviceid_node() and fix caller Peng Fan (OSS)
2026-02-27 8:18 ` [PATCH 2/3] NFS: flexfilelayout: Mark err as __maybe_unused in ff_layout_io_track_ds_error Peng Fan (OSS)
2026-02-27 8:18 ` [PATCH 3/3] NFS: nfs4proc: Mark ptr as __maybe_unused in nfs4_proc_create_session Peng Fan (OSS)
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=20260227-nfs-v1-0-2a6ea2ca8528@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=trondmy@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