From: Petr Vorel <petr.vorel@gmail.com>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: ps.report@gmx.net, yann.morin@orange.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/7] support/kconfig: update to kconfig from Linux 7.2.9
Date: Sat, 17 Oct 2026 00:47:15 +0200 [thread overview]
Message-ID: <20261016224715.GF331129@pevik> (raw)
In-Reply-To: <20261010151121.876133-5-titouan.christophe@mind.be>
Hi Titouan,
> Many changes happened in upstream kconfig since the version we had
> in tree so far, which was derived from Linux 4.19. Here are some of
> the important ones:
> - images for the graphical frontends are now in dedicated .xpm files
> in the icons/ directory (previously they were embedded in .c files)
> - some header-only data structure helpers (hashtable, list, ...) that
> are used in other tools in the linux tree have been put in an include/
> directory, which must now be copied in Buildroot as well
> - Buildroot specific patches have been heavily reworked (some removed)
> to apply on this new version
> - Upstream dropped support for including files within a "choice" context,
> but this mechanism is used in Buildroot. Add a patch to continue
> allowing that in our tree.
> Finally, update README.buildroot to reflect these changes.
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
This would deserve a lot of testing (to prevent revert of whole approach in the
future due hidden bugs).
Kind regards,
Petr
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-16 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 15:11 [Buildroot] [PATCH 0/7] Update kconfig inrastructure to Linux 7.2.9 Titouan Christophe via buildroot
2026-10-10 15:11 ` [Buildroot] [PATCH 1/7] Makefile: always use a base config file for defconfig Titouan Christophe via buildroot
2026-10-16 21:30 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 2/7] */Config.in: use the new $(VAR) syntax Titouan Christophe via buildroot
2026-10-16 22:17 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 3/7] */Config.in: replace bool entries with prompt within all choices Titouan Christophe via buildroot
2026-10-16 22:25 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 5/7] package/openssl: move libopenssl/libressl options out of the choice Titouan Christophe via buildroot
2026-10-16 22:51 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 6/7] docs/manual: add migration notes for changes in the kconfig syntax Titouan Christophe via buildroot
2026-10-16 22:53 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 7/7] Makefile: add new target "yellowconfig" based on kconfiglib Titouan Christophe via buildroot
2026-10-16 21:44 ` Petr Vorel
2026-10-11 19:12 ` [Buildroot] [PATCH 0/7] Update kconfig inrastructure to Linux 7.2.9 Petr Vorel
2026-10-11 19:30 ` Titouan Christophe via buildroot
2026-10-16 21:29 ` Petr Vorel
[not found] ` <20261010151121.876133-5-titouan.christophe@mind.be>
2026-10-16 22:47 ` Petr Vorel [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=20261016224715.GF331129@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
--cc=yann.morin@orange.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