From: Thomas Pedersen <thomas@adapt-ip.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: hauke@hauke-m.de, backports@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH 0/4] backports: use kconfig from git subtree
Date: Thu, 12 May 2022 15:25:56 -0700 [thread overview]
Message-ID: <33970b2070d31b3150acc41b1ddbf88e@adapt-ip.com> (raw)
In-Reply-To: <20220204214131.1306843-1-mcgrof@kernel.org>
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/
--
thomas
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2022-05-12 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 21:41 [PATCH 0/4] backports: use kconfig from git subtree Luis Chamberlain
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 ` Thomas Pedersen [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=33970b2070d31b3150acc41b1ddbf88e@adapt-ip.com \
--to=thomas@adapt-ip.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=johannes@sipsolutions.net \
--cc=mcgrof@kernel.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 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).