From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>,
Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2] package/util-linux: bump to 2.41
Date: Mon, 21 Apr 2025 23:31:59 +0200 [thread overview]
Message-ID: <20250421233159.792b17e7@windsurf> (raw)
In-Reply-To: <CACXRmJioVq7PUwBkCPNj0k-47hrJ_vtgVYtzp+_84ZgimDe9CA@mail.gmail.com>
Hello,
On Wed, 2 Apr 2025 22:27:39 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> So two things to fix.
So, I'm going to mark this patch as Changes Requested. Do you intend to
work on solving those remaining build issues?
Thanks a lot!
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-04-21 21:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 10:16 [Buildroot] [PATCH v1] package/util-linux: bump to 2.41 Thomas Devoogdt
2025-03-26 13:24 ` Waldemar Brodkorb
2025-04-02 8:26 ` [Buildroot] [PATCH v2] " Thomas Devoogdt
2025-04-02 10:18 ` Thomas Devoogdt
2025-04-02 11:08 ` Waldemar Brodkorb
2025-04-02 17:08 ` Thomas Devoogdt
2025-04-02 17:40 ` Waldemar Brodkorb
2025-04-02 18:56 ` Waldemar Brodkorb
2025-04-02 20:27 ` Thomas Devoogdt
2025-04-21 21:31 ` Thomas Petazzoni via buildroot [this message]
2025-04-22 7:32 ` Thomas Devoogdt
2025-04-22 7:55 ` Thomas Petazzoni via buildroot
2025-04-22 7:59 ` [Buildroot] [PATCH v3] " Thomas Devoogdt
2025-04-22 8:40 ` Thomas Petazzoni via buildroot
2025-06-25 14:55 ` Marcus Hoffmann via buildroot
2025-06-26 19:49 ` Thomas Devoogdt
2025-06-26 19:47 ` [Buildroot] [PATCH v4] package/util-linux: bump to 2.41.1 Thomas Devoogdt
2025-07-05 17:26 ` Julien Olivain 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=20250421233159.792b17e7@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.devoogdt@barco.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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.