mbox series

[0/4] backports: use kconfig from git subtree

Message ID 20220204214131.1306843-1-mcgrof@kernel.org (mailing list archive)
Headers show
Series backports: use kconfig from git subtree | expand

Message

Luis Chamberlain Feb. 4, 2022, 9:41 p.m. UTC 
Updated version of kconfig has always been a challenge.
One of the pain points is figuring out how to do this well
and what files / Makefile lines to edit. Part of this is
because we don't carry all the kernel's helpers on our kconfig
helper. The other aspect which makes it hard is figuring out
adjustments of missing files, renames, and updates to things to
make things compile.

The kconfig git subtree effort aims at helping with this. It
figures all the above out for you and all we need to do is just
declare where we keep the kconfig data on, and then include a
Makefile from the git subtree code into our project. That's it.

Of course then there may also be fixes to our Kconfig files for
deprecated features, but that's expected collateral. This drops
our version of kconfig and embraces the git subtree version
whic is now up to date with the latest kconfig from linux-next
next-20220204.

That makes for 4 projects now using this new kconfig git subtree:

 * init-kconfig
 * kdevops
 * fio-tests
 * backports

I've tested this by generating a backport using Linux stable
kernel v5.15.8. At least make menuconfig works.

Luis Chamberlain (4):
  backport/kconf: remove our version of kconfig
  Squashed 'backport/kconf/' content from commit 98bda615
  kconfig: fix backport syntax to work with linux-next next-20220204
  Makefile.subtrees: document how to update kconfig

Comments

Thomas Pedersen May 12, 2022, 10:25 p.m. UTC | #1 
On 2022-02-04 13:41, Luis Chamberlain wrote:
> Updated version of kconfig has always been a challenge.
> One of the pain points is figuring out how to do this well
> and what files / Makefile lines to edit. Part of this is
> because we don't carry all the kernel's helpers on our kconfig
> helper. The other aspect which makes it hard is figuring out
> adjustments of missing files, renames, and updates to things to
> make things compile.

Yep. When refreshing the integration mode patches[1] I went through the 
following process:

1) Realize kconfig changes are needed
2) Check if Luis' patches were merged
3) Decide to pull in new kconfig changes manually just to get unblocked
4) Wonder which kconfig files are actually needed.

> The kconfig git subtree effort aims at helping with this. It
> figures all the above out for you and all we need to do is just
> declare where we keep the kconfig data on, and then include a
> Makefile from the git subtree code into our project. That's it.

So, from my point of view this seems like a fine change.

[1] 
https://lore.kernel.org/all/YfyN2GnfeANyNhaS@bombadil.infradead.org/T/