From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: ansible.cfg pathname setting
Date: Thu, 28 Aug 2025 11:59:01 -0700 [thread overview]
Message-ID: <aLCm9Z_tdmjaP0a_@bombadil.infradead.org> (raw)
In-Reply-To: <0e9b12aa-64f5-44db-af50-03779b590182@oracle.com>
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? 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?
Luis
next prev parent reply other threads:[~2025-08-28 18:59 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 [this message]
2025-08-28 19:08 ` Chuck Lever
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=aLCm9Z_tdmjaP0a_@bombadil.infradead.org \
--to=mcgrof@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