From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next] package/e2fsprogs: allow uclibc toolchains for e4defrag
Date: Mon, 19 Aug 2024 13:17:24 +0200 [thread overview]
Message-ID: <20240819131724.461ee618@windsurf> (raw)
In-Reply-To: <ZsHFY4nLrUaZgEDD@waldemar-brodkorb.de>
On Sun, 18 Aug 2024 11:56:51 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Since 2014 e4defrag was only available for musl/glibc
> toolchains in commit d770abad335a85884cfc2ec7574a331c29522810.
>
> I believe sync_file_range() was already available in 2015 in the uClibc time.
>
> So enable e4defrag. Tested in Qemu on a ext4 filesystem.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/e2fsprogs/Config.in | 5 -----
> 1 file changed, 5 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-19 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 9:56 [Buildroot] [PATCH next] package/e2fsprogs: allow uclibc toolchains for e4defrag Waldemar Brodkorb
2024-08-19 11:17 ` Thomas Petazzoni via buildroot [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=20240819131724.461ee618@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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