public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 0/2] Set TOPDIR at run time
Date: Thu, 28 Aug 2025 16:28:25 -0400	[thread overview]
Message-ID: <20250828202827.3253499-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

A few recent changes have been difficult to integrate into my
current CI infrastructure. Here are a couple of ideas on how to
stretch in a couple of areas to help my particular arrangement.

Note that I would need to handle the inventory file location in a
similar way: add a boolean Kconfig option to use a sensible default
location rather than baking a fixed pathname into the kdevops
.config. So, work in progress here.

Thoughts and alternatives are welcome. Even the Internet standard
response ("you're doing it wrong") is OK.

Chuck Lever (2):
  Set TOPDIR_PATH and generate its sha256sum at run time
  ansible.cfg: generate an ansible.cfg file in TOPDIR

 Kconfig                      | 15 ---------------
 Makefile                     | 12 ++++++++++++
 kconfigs/Kconfig.ansible_cfg | 12 ++++++++++++
 scripts/gen-hosts.Makefile   |  1 +
 scripts/ssh.Makefile         |  4 ++--
 5 files changed, 27 insertions(+), 17 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-08-28 20:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 20:28 Chuck Lever [this message]
2025-08-28 20:28 ` [RFC PATCH 1/2] Set TOPDIR_PATH and generate its sha256sum at run time Chuck Lever
2025-08-29 11:19   ` Luis Chamberlain
2025-08-29 13:38     ` Chuck Lever
2025-09-01 11:29   ` Daniel Gomez
2025-08-28 20:28 ` [RFC PATCH 2/2] ansible.cfg: generate an ansible.cfg file in TOPDIR Chuck Lever
2025-08-29 11:23   ` Luis Chamberlain
2025-08-29 13:39     ` Chuck Lever
2025-08-29 16:59       ` Luis Chamberlain
2025-09-01 12:00   ` Daniel Gomez
2025-09-01 15:03     ` Chuck Lever
2025-09-01 17:07       ` Daniel Gomez

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=20250828202827.3253499-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.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