From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A31262FA0EE for ; Wed, 17 Sep 2025 03:40:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758080402; cv=none; b=IWO1WTZMgV/TsnjeKGCtXbdtY7WzwEbstMETKVqxpw+FVcEmw9Wz5TqWLcTrgC3PFhXAtRIRo8hVioiejPwe3IcSL9cO1HJ0qs2iaEoFIllG7u3SbHzoCEjMhr1897BZzpw9EeAb3whSoGjw2nq7ZMc4ndxrIl2NyR87FKMqnOk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758080402; c=relaxed/simple; bh=mKCTlZxcgjfPz69YFnAraW9b9323OyEpId6Zknrruu0=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type; b=NhLZcu8XNhQKRJ2Vw2tiiv3FD159pK7iM5kS3C/OcqBDZLyE/LfHZHNI4/t9t40GZhTc9l6GMYubDh6BkxK7bt/h9YTVkIeS5fZF8N0Vw3xp8q7n8qAYFj/ue13tYp/zfOTLNdgR6VtuOqFNlNcT5e5GrXPmGnjJ71xTb/tRucg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=FoM/Dl6a; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="FoM/Dl6a" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 85524C4CEEB; Wed, 17 Sep 2025 03:40:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1758080402; bh=mKCTlZxcgjfPz69YFnAraW9b9323OyEpId6Zknrruu0=; h=Date:Subject:To:References:From:In-Reply-To:From; b=FoM/Dl6aypCBMOrm/MfyuF/pbfRSIJajGyRGi+UNxn9CXd1w0vqgwAf0HKiYDfIvR nV9Ssah5yTZZXekvVzC8MUneAmM6x9XAASUpJzk5J89ZC0cOBKB2Y9WVdkt7+Z8Dqt /NpqXVlr5p8dmXaQVsBZ+uWgDEN5+jgm9kncG8+qNC2dKx03o5ZLkW740/WdnmX5lZ xtG/+2rrP+9LAzfAYEVn+llSDsbiAHFY0etYfFsYeb5HtBtvDDMNr9sRv5GGrmE/LJ wX88tOgyGD2mYH4m7gdgs0B2Oj4QMY58SBI2MK4fl6I5btaTjdJ+vz3FhPQKwnB7ns UbrGGPoLB8J3g== Message-ID: <25fa4505-78fd-469b-a076-ef7d0aa83103@kernel.org> Date: Tue, 16 Sep 2025 20:40:00 -0700 Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v4 4/8] aws: integrate dynamic Kconfig generation with make targets To: Luis Chamberlain , Daniel Gomez , kdevops@lists.linux.dev References: <20250917003451.2318229-1-mcgrof@kernel.org> <20250917003451.2318229-5-mcgrof@kernel.org> Content-Language: en-US From: Chuck Lever Organization: kernel.org In-Reply-To: <20250917003451.2318229-5-mcgrof@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 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. -- Chuck Lever