From: Markus Mayer via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Markus Mayer <mmayer@broadcom.com>, Julien Olivain <ju.o@free.fr>,
Bernd Kuhls <bernd@kuhls.net>,
Buildroot List <buildroot@buildroot.org>
Subject: [Buildroot] [PATCH 0/1] package/e2fsprogs: fix fsverity build error slightly differently
Date: Thu, 4 Dec 2025 16:30:03 -0800 [thread overview]
Message-ID: <20251205003008.153577-1-mmayer@broadcom.com> (raw)
This is the follow-up to the mailing list discussion at [1].
The only thing I undid about Thomas' patch was to remove
0001-configure.ac-check-for-FS_IOC_READ_VERITY_METADATA-a.patch
The change to e2fsprogs.mk remains with the comment slightly tweaked.
Please feel free to adjust the commit message if needed.
[1]: https://lists.buildroot.org/pipermail/buildroot/2025-November/790482.html
Markus Mayer (1):
package/e2fsprogs: fix fsverity build error slightly differently
...ck-for-FS_IOC_READ_VERITY_METADATA-a.patch | 103 --------------
.../0001-lib-add-kern_compat.h.patch | 134 ++++++++++++++++++
package/e2fsprogs/0002-Generated-files.patch | 63 ++++++++
package/e2fsprogs/e2fsprogs.mk | 4 +-
4 files changed, 199 insertions(+), 105 deletions(-)
delete mode 100644 package/e2fsprogs/0001-configure.ac-check-for-FS_IOC_READ_VERITY_METADATA-a.patch
create mode 100644 package/e2fsprogs/0001-lib-add-kern_compat.h.patch
create mode 100644 package/e2fsprogs/0002-Generated-files.patch
--
2.51.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-12-05 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 0:30 Markus Mayer via buildroot [this message]
2025-12-05 0:30 ` [Buildroot] [PATCH 1/1] package/e2fsprogs: fix fsverity build error slightly differently Markus Mayer via buildroot
2026-02-02 13:18 ` Thomas Petazzoni 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=20251205003008.153577-1-mmayer@broadcom.com \
--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 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.