From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Markus Mayer <mmayer@broadcom.com>
Cc: Julien Olivain <ju.o@free.fr>,
Buildroot List <buildroot@buildroot.org>,
Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH] package/e2fsprogs: fix build with headers >= 5.10 and < 5.12
Date: Sat, 29 Nov 2025 22:17:13 +0100 [thread overview]
Message-ID: <20251129221713.364a5085@windsurf> (raw)
In-Reply-To: <CAGt4E5tGGkOAtDYysD2DcusQZNhfb6CV5mtJPPNn_oWwr+M04g@mail.gmail.com>
On Fri, 28 Nov 2025 13:16:24 -0800
Markus Mayer <mmayer@broadcom.com> wrote:
> According to [1] and [2], e2fsprogs does the right thing and will
> propagate the "not supported" error. I'll see if I can set up a test
> case that will trigger this function call, so I can verify the actual
> behaviour.
Sounds good to me, you don't need to do a formal test to verify the
actual behavior.
How do we proceed? You send a follow-up patch that improves mine? I've
anyway had no feedback from upstream.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-11-29 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 13:34 [Buildroot] [PATCH] package/e2fsprogs: fix build with headers >= 5.10 and < 5.12 Thomas Petazzoni via buildroot
2025-11-23 14:16 ` Julien Olivain via buildroot
2025-11-27 19:53 ` Markus Mayer via buildroot
2025-11-28 9:21 ` Thomas Petazzoni via buildroot
2025-11-28 21:16 ` Markus Mayer via buildroot
2025-11-29 21:17 ` Thomas Petazzoni via buildroot [this message]
2025-12-04 21:33 ` Markus Mayer via buildroot
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=20251129221713.364a5085@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
--cc=mmayer@broadcom.com \
--cc=thomas.petazzoni@bootlin.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