From: Petr Vorel <petr.vorel@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nfs-utils: fix printfs format build failure on 64-bits platforms
Date: Sun, 25 Jul 2021 23:11:19 +0200 [thread overview]
Message-ID: <YP3Td024jBRWDVsH@pevik> (raw)
In-Reply-To: <20210725210054.1534823-1-giulio.benetti@benettiengineering.com>
Hi Giulio,
> Add 2 pending upstream patches that have been pointed to nfs-utils
> maintainer to be committed soon. They both fix the build failure on 64-bits
> where time_t is assumed to be a long long when passed to printf("%ld"), but
> that is not always true, so in these patches the author(Petr) uses PRIu64
> tag.
> Fixes:
> http://autobuild.buildroot.net/results/9bc1d43a588338b7395af7bc97535ee16a6ea2d9/
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Cc: Petr Vorel <petr.vorel@gmail.com>
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
Although I'd wait till Monday, when Steve merges them and then add
upstream commit hashes.
Or at least add links from lore.
https://lore.kernel.org/linux-nfs/20210722161545.26923-1-petr.vorel@gmail.com/
https://lore.kernel.org/linux-nfs/20210722161545.26923-2-petr.vorel@gmail.com/
Kind regards,
Petr
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-25 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 21:00 [Buildroot] [PATCH] package/nfs-utils: fix printfs format build failure on 64-bits platforms Giulio Benetti
2021-07-25 21:11 ` Petr Vorel [this message]
2021-07-25 21:15 ` Giulio Benetti
2021-07-28 20:01 ` Thomas Petazzoni
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=YP3Td024jBRWDVsH@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.