From: Luis Chamberlain <mcgrof@kernel.org>
To: hauke@hauke-m.de, backports@vger.kernel.org, mcgrof@kernel.org
Cc: thomas@adapt-ip.com, johannes@sipsolutions.net
Subject: [PATCH 0/4] backports: use kconfig from git subtree
Date: Fri, 4 Feb 2022 13:41:27 -0800 [thread overview]
Message-ID: <20220204214131.1306843-1-mcgrof@kernel.org> (raw)
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
--
2.34.1
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2022-02-04 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 21:41 Luis Chamberlain [this message]
2022-02-04 21:41 ` [PATCH 1/4] backport/kconf: remove our version of kconfig Luis Chamberlain
2022-02-04 21:41 ` [PATCH 2/4] Squashed 'backport/kconf/' content from commit 98bda615 Luis Chamberlain
2022-02-04 21:41 ` [PATCH 3/4] kconfig: fix backport syntax to work with linux-next next-20220204 Luis Chamberlain
2022-02-04 21:41 ` [PATCH 4/4] Makefile.subtrees: document how to update kconfig Luis Chamberlain
2022-02-04 21:43 ` Johannes Berg
2022-02-04 21:44 ` Luis Chamberlain
2022-02-04 21:56 ` Luis Chamberlain
2022-02-04 21:59 ` Johannes Berg
2022-02-04 22:17 ` Luis Chamberlain
2022-02-04 21:43 ` Luis Chamberlain
2022-05-12 22:25 ` [PATCH 0/4] backports: use kconfig from git subtree Thomas Pedersen
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=20220204214131.1306843-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=johannes@sipsolutions.net \
--cc=thomas@adapt-ip.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).