public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Daniel Gomez <da.gomez@kruces.com>, kdevops@lists.linux.dev
Subject: Re: [PATCH 1/2] aws: add dynamic cloud configuration support using AWS CLI
Date: Mon, 8 Sep 2025 11:23:11 -0400	[thread overview]
Message-ID: <7a70cc20-34fa-40e7-9868-eb275d637141@kernel.org> (raw)
In-Reply-To: <aL4C6Ohyd_gJjUjj@bombadil.infradead.org>

On 9/7/25 6:10 PM, Luis Chamberlain wrote:
>> Or to put it another way, for me the merge criteria for this patch is
>> that it can generate a set of working AWS menus that are a superset of
>> what is already in the tree now. I'm not seeing a need to turn this
>> facility on or off. If there is a need for disabling it, can you add it
>> to the patch description or Kconfig help text?
> The only rationale for disabling it is if users relied on old defconfigs
> which may not fit with the new style meant to be dynamic. Some kconfig
> symbols may have changed. I have not vetted them all. However, if we
> don't really have users (I don't think we do) of AWS defconfigs, perhaps
> this is a non-issue we can wholely replace the old stuff with the new
> dynamic stuff.
> 
> I just decided to go with the conservative approach so we can discuss
> this a bit more.
> 
> My spidy senses tell me we should be able to full on replace the old
> static stuff with a new world order. But more broad users of cloud
> suport should chime in. I think our larger user base may be OCI users.
> So for OCI I suspect more care is needed. For AWS I think we're safe
> to replace old static files for the dynamically generated ones.

That is my take as well: Chandan, you, and I are the only cloud-based
kdevops users atm.


-- 
Chuck Lever

  parent reply	other threads:[~2025-09-08 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07  4:23 [PATCH 0/2] aws: add dynamic kconfig support Luis Chamberlain
2025-09-07  4:23 ` [PATCH 1/2] aws: add dynamic cloud configuration support using AWS CLI Luis Chamberlain
2025-09-07 17:24   ` Chuck Lever
2025-09-07 22:10     ` Luis Chamberlain
2025-09-07 22:12       ` Luis Chamberlain
2025-09-08 14:12       ` Chuck Lever
2025-09-08 14:21       ` Chuck Lever
2025-09-08 15:23       ` Chuck Lever [this message]
2025-09-08 20:22         ` Luis Chamberlain
2025-09-07  4:23 ` [PATCH 2/2] aws: enable GPU AMI support for GPU instances 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=7a70cc20-34fa-40e7-9868-eb275d637141@kernel.org \
    --to=cel@kernel.org \
    --cc=da.gomez@kruces.com \
    --cc=kdevops@lists.linux.dev \
    --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