public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH RFC 6/6] playbooks: add kconfig support
Date: Fri, 28 Mar 2025 15:58:50 -0700	[thread overview]
Message-ID: <Z-cpqu2OouHOeto_@bombadil.infradead.org> (raw)
In-Reply-To: <20250328-kconfig-env-with-ansible-v1-6-3231c0272457@samsung.com>

On Fri, Mar 28, 2025 at 08:56:19PM +0000, Daniel Gomez wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
> 
> Add kconfig playbook to generate Kconfig environment with Ansible.
> 
> The output will be a Kconfig fragment (.env.config) that will be merged
> with existing configuration file.
> 
> Add .env.config to the list of git-ignored files.
> 
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>

I think I get what this is doing and this seems pretty awesome!
Essentially we replace the kdevops Kconfigs which rely on scripts
with ansible calls which can rely on jinja2 template parsing on the
fly. This works especially well for use given we alreayd process
config symbols to yaml entries and always read them for ansible
playbooks.

While we could explore adapting this for complex scripts we use
like the ones which try to check your existing libvirt pools,
a simple jinja2 processing trick might be nicer to help us scale
with more symbols, otherwise kconfig will be rather slow. So,
any chance we might be able to leverage some regular python jinja2
thing which perhaps upstream Linux can also embrace?

Also I think it makes sense to combine this and patch #5, and also
you forgot to remove the script this is replacing?

  Luis

  reply	other threads:[~2025-03-28 22:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 20:56 [PATCH RFC 0/6] Generate Kconfig environment in Ansible Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 1/6] merge_config: add fragment support from kernel Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 2/6] scripts/kconfig/kconfig.Makefile: extend simple-targets Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 3/6] kconfig-fragments: add docs and fragments folder Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 4/6] kconfig-env: generate kconfig environment Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 5/6] kconfig: env: add support Daniel Gomez
2025-03-28 20:56 ` [PATCH RFC 6/6] playbooks: add kconfig support Daniel Gomez
2025-03-28 22:58   ` Luis Chamberlain [this message]
2025-03-31  6:54     ` Daniel Gomez
2025-03-31  7:32       ` Luis Chamberlain
2025-03-31 18:31         ` Daniel Gomez
2025-04-01 21:02           ` Luis Chamberlain
2025-04-04 20:33             ` Daniel Gomez
2025-04-07  4:03               ` Luis Chamberlain
2025-04-14 10:58                 ` Daniel Gomez
2025-04-23  6:01                   ` Luis Chamberlain

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=Z-cpqu2OouHOeto_@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=da.gomez@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=kdevops@lists.linux.dev \
    --cc=masahiroy@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