From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs: regenerate all defconfigs
Date: Sat, 21 Sep 2024 11:52:37 +0200 [thread overview]
Message-ID: <Zu6XZXX1bCgd2jFP@landeda> (raw)
In-Reply-To: <e35baa79-3f30-4a85-b811-d3d662e6f96a@grenoble.cnrs.fr>
Edgar, All,
On 2024-09-20 10:01 +0200, Edgar Bonet spake thusly:
> Yesterday, Yann E. MORIN wrote:
> > This is a mechanical change, achieved by running:
> > $ for cfg in configs/*_defconfig; do
> > (make "${cfg##*/}" && make savedefconfig) || break
> > done
> The problem with using `make savedefconfig` for this is that, if we are
> using the latest supported kernel headers (currently 6.10), the line
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_10=y
>
> gets removed from the defconfig. This is an issue because, whenever
> Buildroot adds support for headers 6.11, the defconfig will
> automatically default to those.
Indeed, very good catch!
> In fact,
> docs/manual/adding-board-support.adoc explicitly asks contributors to:
> set the custom kernel headers series to match your kernel version
> (+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_*+).
Yes, I forgot to update the documentation accordingly. But in
retrospect, I can just now say "I just wanted feedback!" ;-)
> In this patch, the issue affects six defconfigs, namely:
> beagleplay_defconfig
> imx8mn_bsh_smm_s2_defconfig
> imx8mn_bsh_smm_s2_pro_defconfig
> mx6udoo_defconfig
> ti_am62x_sk_defconfig
> ti_am64x_sk_defconfig
I'll send a new patchset that actually allows using savedefconfig; I
just need to think a little bit more about it (I think I have a
solution).
Thanks for noticing. 👍
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-21 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 20:20 [Buildroot] [PATCH] configs: regenerate all defconfigs Yann E. MORIN
2024-09-20 8:01 ` Edgar Bonet
2024-09-21 9:52 ` Yann E. MORIN [this message]
2024-09-21 17:01 ` Edgar Bonet
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=Zu6XZXX1bCgd2jFP@landeda \
--to=yann.morin.1998@free.fr \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
/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.