From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] Revert "e2fsprogs: fix posix_fadvise() signature mismatch"
Date: Mon, 20 Jan 2014 22:37:49 +0100 [thread overview]
Message-ID: <8761pejpw2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <10f996cb2545050f65e8a108573e9ee7bfd9e41c.1389594195.git.baruch@tkos.co.il> (Baruch Siach's message of "Mon, 13 Jan 2014 08:26:14 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> This reverts commit c3d690166c4533bc83500a22a43783193fbc27f9.
> The real cause of problem is missing posix_fadvise() implementation in uClibc
> for xtensa. This has now been fixed with the uclibc version bump. The internal
> e2fsprogs posix_fadvise() implementation is broken on 32bit systems anyway, and
> upstream has removed it.
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-20 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 6:26 [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Baruch Siach
2014-01-13 6:26 ` [Buildroot] [PATCH v2 1/3] uclibc: bump " Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 2/3] uclibc: xtensa: fix posix_spawn autoconf detection Baruch Siach
2014-01-15 13:31 ` Baruch Siach
2014-01-15 14:30 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 3/3] Revert "e2fsprogs: fix posix_fadvise() signature mismatch" Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard [this message]
2014-01-13 8:13 ` [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Thomas Petazzoni
2014-01-13 8:23 ` Baruch Siach
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=8761pejpw2.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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