From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/pixman: fix NEON support on AArch64
Date: Sat, 27 Dec 2025 16:15:46 +0100 [thread overview]
Message-ID: <20251227161546.4a0386b6@windsurf> (raw)
In-Reply-To: <20251217-pixman-aarch64-neon-fix-v2-1-e0889825b157@armadeus.com>
Hello Sébastien,
On Wed, 17 Dec 2025 12:56:13 +0100
Sébastien Szymanski <sebastien.szymanski@armadeus.com> wrote:
> The test to enable NEON on AArch64 is as following:
>
> ifeq ($(BR2_aarch64)$(BR2_ARM_CPU_HAS_NEON),yy)
>
> It cannot be to true as $(BR2_aarch64) and $(BR2_ARM_CPU_HAS_NEON) are
> mutually exclusive. NEON is compulsory on AArch64 so remove
> $(BR2_ARM_CPU_HAS_NEON) from the test.
>
> Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
> ---
> Changes in v2:
> * fix commit title (package/pixman: instead of pixman:)
> * Remove "cherry picked from..." line from the commit log
> * add "Backport to:" note
> * Link to v1: https://lore.kernel.org/r/20251217-pixman-aarch64-neon-fix-v1-1-3a6aa820097e@armadeus.com
> ---
> Backport to: 2025.11.x, 2025.02.x
> ---
> package/pixman/pixman.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master after slightly improving the commit message to point
to the commit which introduced the problem.
Thanks a lot!
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
next prev parent reply other threads:[~2025-12-27 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:56 [Buildroot] [PATCH v2] package/pixman: fix NEON support on AArch64 Sébastien Szymanski
2025-12-27 15:15 ` Thomas Petazzoni via buildroot [this message]
2026-01-07 17:49 ` Arnout Vandecappelle 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=20251227161546.4a0386b6@windsurf \
--to=buildroot@buildroot.org \
--cc=sebastien.szymanski@armadeus.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