From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Daniel Gomez <da.gomez@kruces.com>, kdevops@lists.linux.dev
Subject: Re: [PATCH v4 4/8] aws: integrate dynamic Kconfig generation with make targets
Date: Wed, 17 Sep 2025 00:05:07 -0700 [thread overview]
Message-ID: <aMpdo8s1MUIX1TLw@bombadil.infradead.org> (raw)
In-Reply-To: <25fa4505-78fd-469b-a076-ef7d0aa83103@kernel.org>
On Tue, Sep 16, 2025 at 08:40:00PM -0700, Chuck Lever wrote:
> On 9/16/25 5:34 PM, Luis Chamberlain wrote:
> > Add Makefile integration for AWS dynamic Kconfig generation using
> > Chuck's scripts with the optimized wrapper. This provides:
> >
> > - make cloud-config-aws: Generate AWS Kconfig files
> > - make cloud-update-aws: Clear cache and regenerate fresh data
> > - make cloud-config: Now includes AWS generation
> > - make cloud-update: Refreshes all cloud provider data
> > - make clean-cloud-config-aws: Clean generated AWS files
> >
> > The integration properly manages AWS Kconfig files alongside Lambda Labs
> > configurations and ensures empty files exist before Kconfig runs to
> > prevent sourcing errors.
> >
> > Also update generate_cloud_configs.py to call the AWS generator and
> > provide summary statistics about available AWS resources.
> >
> > Generated-by: Claude AI
> > Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
>
> Yes, this is exactly what I was thinking -- add in the menu generator
> scripts first and then construct make targets to drive them.
>
> But I've been working on the scripts themselves and have new smaller
> versions of the locations and instance menu generators. Let me flesh
> those out a little more (and finish the AMI menu generator) then I will
> post here and we can integrate.
No need, just merge your changes :) Full steam ahead!
Luis
next prev parent reply other threads:[~2025-09-17 7:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 0:34 [PATCH v4 0/8] aws: add dynamic kconfig support Luis Chamberlain
2025-09-17 0:34 ` [PATCH v4 1/8] aws: prevent SSH key conflicts across multiple kdevops directories Luis Chamberlain
2025-09-17 3:36 ` Chuck Lever
2025-09-17 0:34 ` [PATCH v4 2/8] terraform/aws: Add scripts to gather provider resource information Luis Chamberlain
2025-09-17 0:34 ` [PATCH v4 3/8] aws: add optimized Kconfig generator using Chuck's scripts Luis Chamberlain
2025-09-17 3:58 ` Chuck Lever
2025-09-17 0:34 ` [PATCH v4 4/8] aws: integrate dynamic Kconfig generation with make targets Luis Chamberlain
2025-09-17 3:40 ` Chuck Lever
2025-09-17 7:05 ` Luis Chamberlain [this message]
2025-09-17 0:34 ` [PATCH v4 5/8] aws: add cloud billing support with make cloud-bill Luis Chamberlain
2025-09-17 0:34 ` [PATCH v4 6/8] aws: replace static Kconfig files with dynamically generated ones Luis Chamberlain
2025-09-17 0:34 ` [PATCH v4 7/8] aws: add GPU instance defconfigs for AI/ML workloads Luis Chamberlain
2025-09-17 0:34 ` [PATCH v4 8/8] docs: add documentation for dynamic cloud configuration 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=aMpdo8s1MUIX1TLw@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
/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