Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: Buildroot development <buildroot@buildroot.org>,
	 Biagio Montaruli <biagio.hkr@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/3] board/acmesystems/acqua-a5: remove linux-headers.hash
Date: Sun, 25 Oct 2026 21:50:06 +0100	[thread overview]
Message-ID: <at5rdrCoFUZmJCbE@windsurf> (raw)
In-Reply-To: <f90ec3b4-bd18-4f71-b4fc-eb2c385a9978@grenoble.cnrs.fr>

On Sat, Oct 24, 2026 at 11:15:44PM +0200, Edgar Bonet via buildroot wrote:
> Since commit a8b9c6f9f512 ("configs/acmesystems_acqua_a5_*: switch to
> Bootlin glibc stable toolchain"), the acmesystems_acqua_a5_* defconfigs
> do not build a Buildroot toolchain anymore. Hence they do not depend on
> linux-headers.
> 
> Remove the symlink linux-headers.hash -> ../linux/linux.hash.
> 
> Fixes: a8b9c6f9f512cc3ef18956b53a99b93ba74a9e8f ("configs/acmesystems_acqua_a5_*: switch to Bootlin glibc stable toolchain")
> Signed-off-by: Edgar Bonet <bonet@grenoble.cnrs.fr>

Series applied to master, thanks!

Best regards,

Thomas Petazzoni
-- 
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

      parent reply	other threads:[~2026-10-25 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 21:15 [Buildroot] [PATCH 1/3] board/acmesystems/acqua-a5: remove linux-headers.hash Edgar Bonet via buildroot
2026-10-24 21:28 ` [Buildroot] [PATCH 2/3] configs/acmesystems_acqua_a5_*: set issue and hostname Edgar Bonet via buildroot
2026-10-24 21:30 ` [Buildroot] [PATCH 3/3] configs/acmesystems_acqua_a5_*: bump to Linux 6.18.58 Edgar Bonet via buildroot
2026-10-25 20:50 ` Thomas Petazzoni via buildroot [this message]

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=at5rdrCoFUZmJCbE@windsurf \
    --to=buildroot@buildroot.org \
    --cc=biagio.hkr@gmail.com \
    --cc=bonet@grenoble.cnrs.fr \
    --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