From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/ima-evm-utils: fix build on musl
Date: Thu, 23 Jul 2020 14:11:40 +0200 [thread overview]
Message-ID: <20200723141140.0af45237@windsurf.home> (raw)
In-Reply-To: <20200722193532.32150-3-petr.vorel@gmail.com>
On Wed, 22 Jul 2020 21:35:32 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> Fixes:
> br-arm-cortex-a9-musl [ 7/44]: FAILED
> br-i386-pentium-mmx-musl [12/44]: FAILED
> br-x86-64-musl [34/44]: FAILED
> linaro-aarch64 [36/44]: FAILED
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
Same question as for PATCH 2/3: is this needed after the 1.3 version
bump, or is this needed independently of the version bump.
There are two possibilities:
- The fixes of PATCH 2/3 and PATCH 3/3 are needed independently of the
version bump. In this case, they should be in the patch series
*before* the 1.3 version bump, so that we know those fixes can for
example be backported to our LTS/stable branch.
- The fixes of PATCH 2/3 and PATCH 3/3 are needed due to
issues/regressions introduced by the 1.3 version bump. In this case,
they should be part of the version bump patch itself, to not break
bisectability.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-23 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 19:35 [Buildroot] [PATCH 1/3] package/ima-evm-utils: bump version to 1.3 Petr Vorel
2020-07-22 19:35 ` [Buildroot] [PATCH 2/3] package/ima-evm-utils: fix build for old compilers Petr Vorel
2020-07-23 12:10 ` Thomas Petazzoni
2020-07-22 19:35 ` [Buildroot] [PATCH 3/3] package/ima-evm-utils: fix build on musl Petr Vorel
2020-07-23 12:11 ` Thomas Petazzoni [this message]
2020-07-23 20:03 ` Petr Vorel
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=20200723141140.0af45237@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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