From: Daniel Gomez <da.gomez@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH RFT 0/6] Fix Ansible warnings and simplify build dependency order
Date: Tue, 23 Sep 2025 22:12:47 +0200 [thread overview]
Message-ID: <7c62f2a4-8c2d-4fe1-a429-b03be01b90a3@kernel.org> (raw)
In-Reply-To: <d2e5a8f5-7141-4718-a795-87d12aa7342c@oracle.com>
On 22/09/2025 16.15, Chuck Lever wrote:
> On 9/22/25 4:13 AM, Daniel Gomez wrote:
> I didn't look closely at the details, but this series makes a world
> of sense.
>
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Thanks! Applied and pushed.
prev parent reply other threads:[~2025-09-23 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 11:13 [PATCH RFT 0/6] Fix Ansible warnings and simplify build dependency order Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 1/6] Makefile: fix target " Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 2/6] gen_hosts: add localhost to generic workflow template Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 3/6] ansible_cfg: fix Python interpreter discovery warning Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 4/6] Makefile: remove warnings from ANSIBLE_CFG_FILE target Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 5/6] Makefile: simplify KDEVOPS_NODES ansible-playbook call Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 6/6] Makefile: add explicit connection for inventory generation Daniel Gomez
2025-09-22 14:15 ` [PATCH RFT 0/6] Fix Ansible warnings and simplify build dependency order Chuck Lever
2025-09-23 20:12 ` Daniel Gomez [this message]
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=7c62f2a4-8c2d-4fe1-a429-b03be01b90a3@kernel.org \
--to=da.gomez@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=da.gomez@samsung.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