From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>,
dagomez <dagomez@example.com>
Subject: Re: [PATCH RFC 0/8] Refactor CI
Date: Tue, 23 Sep 2025 18:14:35 -0700 [thread overview]
Message-ID: <aNNF-1tc7rtI0FH4@bombadil.infradead.org> (raw)
In-Reply-To: <20250923-ci-refactor-v1-0-51e5ad6773e4@samsung.com>
On Tue, Sep 23, 2025 at 11:13:04PM +0200, Daniel Gomez wrote:
> Refactor the .github/ CI setup into modular and reusable workflows and
> actions. This makes it possible to share modules from kdevops repo and
> reuse them in other GitHub projects.
Thanks! Applied and pushed.
Luis
prev parent reply other threads:[~2025-09-24 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 21:13 [PATCH RFC 0/8] Refactor CI Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 1/8] base_image: optimize VM image copying with reflinks and fix same-file handling Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 2/8] kconfig: add KDEVOPS_MAKE_VERBOSE option for persistent verbose output Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 3/8] defconfig: add ci fragment Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 4/8] ansible: enhance DIY callback output format for improved readability Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 5/8] ansible: add profile_tasks callback timing analysis support Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 6/8] scripts: fix CI_WORKFLOW basename mapping Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 7/8] fstests: fix ansible_host undefined error Daniel Gomez
2025-09-23 21:13 ` [PATCH RFC 8/8] github: refactor into reusable actions and workflows Daniel Gomez
2025-09-24 1:14 ` Luis Chamberlain [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=aNNF-1tc7rtI0FH4@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dagomez@example.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