From: Chuck Lever <chuck.lever@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: ansible.cfg pathname setting
Date: Thu, 28 Aug 2025 15:08:48 -0400 [thread overview]
Message-ID: <9a4b02fa-090e-42cb-b381-77950e90d7b3@oracle.com> (raw)
In-Reply-To: <aLCm9Z_tdmjaP0a_@bombadil.infradead.org>
On 8/28/25 2:59 PM, Luis Chamberlain wrote:
> On Thu, Aug 28, 2025 at 12:41:08PM -0400, Chuck Lever wrote:
>> Any opinions about this idea? I can build it if folks agree to it.
>
> I tend to just run my own new make defconfig-foo in each directory for
> each workload, so I have opinion on this, but it sounds like perhaps
> a kconfig option is desirable, to perhaps opt-in to let it use current
> working directory for the file?
That's the basic idea. It feels like that would work better "just out
of the shrinkwrap".
> But if it was not generated then via
> make then what would it use? Ie, if you're shaing a built .config to
> other directories without making make then it sounds like a requirement
> is to also share the generated ansible config?
I think that's what I would have to do: include both the .config and
an ansible.cfg in the kdevops branch pulled by each test runner.
That seems to break the idea that the whole configuration is managed
from .config.
--
Chuck Lever
next prev parent reply other threads:[~2025-08-28 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 16:41 ansible.cfg pathname setting Chuck Lever
2025-08-28 18:59 ` Luis Chamberlain
2025-08-28 19:08 ` Chuck Lever [this message]
2025-08-28 19:11 ` Luis Chamberlain
2025-08-28 19:33 ` Chuck Lever
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=9a4b02fa-090e-42cb-b381-77950e90d7b3@oracle.com \
--to=chuck.lever@oracle.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