From: Sean Chang <seanwascoding@gmail.com>
To: nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
trond.myklebust@hammerspace.com, anna@kernel.org
Cc: netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sean Chang <seanwascoding@gmail.com>
Subject: [PATCH v2 0/2] Fix warnings for RISC-V builds
Date: Tue, 17 Feb 2026 01:49:48 +0800 [thread overview]
Message-ID: <20260216174950.455244-1-seanwascoding@gmail.com> (raw)
This series addresses several compiler warnings found when building the
kernel for RISC-V.
The first patch fixes unused variable warnings in the NFS client (including
nfs4proc and flexfilelayout) that occur in certain build configurations.
The second patch fixes a format-truncation warning in the MACB ethernet
driver by ensuring the snprintf output fits within the destination buffer.
v2:
- Split the original treewide patch into subsystem-specific commits.
- Added more detailed commit descriptions to satisfy checkpatch.
Sean Chang (2):
nfs: fix unused variable warnings
net: macb: fix format-truncation warning
drivers/net/ethernet/cadence/macb_main.c | 4 ++--
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 3 ++-
fs/nfs/nfs4proc.c | 2 +-
4 files changed, 6 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2026-02-16 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 17:49 Sean Chang [this message]
2026-02-16 17:49 ` [PATCH v2 1/2] nfs: fix unused variable warnings Sean Chang
2026-02-16 20:06 ` Andrew Lunn
2026-02-17 9:55 ` Sean
2026-02-16 17:49 ` [PATCH v2 2/2] net: macb: fix format-truncation warning Sean Chang
2026-02-16 18:35 ` Andrew Lunn
2026-02-17 17:28 ` Sean Chang
2026-02-17 17:46 ` Andrew Lunn
2026-02-17 19:14 ` Sean Chang
2026-02-17 20:33 ` Andrew Lunn
2026-02-18 12:16 ` Sean Chang
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=20260216174950.455244-1-seanwascoding@gmail.com \
--to=seanwascoding@gmail.com \
--cc=anna@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.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