From: Steve Dickson <steved@redhat.com>
To: Benjamin Coddington <ben.coddington@hammerspace.com>,
liezhi.yang@windriver.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] fh_key_file.c: Fix build error with musl
Date: Mon, 11 May 2026 10:16:58 -0400 [thread overview]
Message-ID: <a033a1da-d186-4996-9d54-b7ac3a2f940c@redhat.com> (raw)
In-Reply-To: <CD3EAA3F-F758-4CAF-A692-065CA82917AC@hammerspace.com>
On 5/8/26 10:08 AM, Benjamin Coddington wrote:
> On 8 May 2026, at 9:57, liezhi.yang@windriver.com wrote:
>
>> From: Robert Yang <liezhi.yang@windriver.com>
>>
>> Fixed:
>> error: implicit declaration of function 'strerror'
>
> Giulio sent a patch for this already:
> https://lore.kernel.org/linux-nfs/20260408173535.3992116-1-giulio.benetti@benettiengineering.com/
>
> Steve D - did you pick that one up yet?
Nope! It was hiding in a bunch of kernel patch
w/out a nfs-utils subject tag.
It is on todo list now...
steved.
prev parent reply other threads:[~2026-05-11 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 13:57 [nfs-utils PATCH] fh_key_file.c: Fix build error with musl liezhi.yang
2026-05-08 14:08 ` Benjamin Coddington
2026-05-11 14:16 ` Steve Dickson [this message]
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=a033a1da-d186-4996-9d54-b7ac3a2f940c@redhat.com \
--to=steved@redhat.com \
--cc=ben.coddington@hammerspace.com \
--cc=liezhi.yang@windriver.com \
--cc=linux-nfs@vger.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