From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-nfs@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Steve Dickson <steved@redhat.com>
Subject: Re: [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+
Date: Thu, 26 Oct 2023 23:18:00 +0200 [thread overview]
Message-ID: <98066647-bcc8-4231-b6d8-2eff4a1d48fe@benettiengineering.com> (raw)
In-Reply-To: <20231026194712.615384-1-pvorel@suse.cz>
Hi Petr,
On 26/10/23 21:47, Petr Vorel wrote:
> interesting, I yesterday sent patch [1] solving the same problem (although it
> might not be that obvious from the patchset name). Let's see which one will be
> taken.
>
> Kind regards,
> Petr
>
> [1] https://lore.kernel.org/linux-nfs/20231025205720.GB460410@pevik/T/#m4c02286afae09318f6b95ff837750708d5065cd5
I totally forgotten to check Patchwork before working on it. Your patch
looks good, better than mine. Maybe you can improve the part of the
syscall because it's not always available. You can then send a patch for
Buildroot too with the patch you've pointed since there you're
nfs-utils package Maintainer too.
--
Giulio Benetti
CEO&CTO@Benetti Engineering sas
next prev parent reply other threads:[~2023-10-26 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:45 [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+ Giulio Benetti
2023-10-26 11:45 ` [nfs-utils 2/2] Drop unused <sys/random.h> Giulio Benetti
2023-10-26 19:47 ` [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+ Petr Vorel
2023-10-26 21:18 ` Giulio Benetti [this message]
2024-10-18 13:13 ` Steve Dickson
2024-10-18 13:43 ` Petr Vorel
2024-10-18 14:37 ` Steve Dickson
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=98066647-bcc8-4231-b6d8-2eff4a1d48fe@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=richard@nod.at \
--cc=steved@redhat.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