From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: patches@lists.linux.dev, amir73il@gmail.com, pankydev8@gmail.com,
tytso@mit.edu, josef@toxicpanda.com, jmeneghi@redhat.com,
jake@lwn.net, mcgrof@kernel.org
Subject: [PATCH 0/4] kdevops: use linux-kdevops for the main tree
Date: Fri, 13 May 2022 12:38:27 -0700 [thread overview]
Message-ID: <20220513193831.4136212-1-mcgrof@kernel.org> (raw)
More just like a heads up as to the next steps from discussions at
LSFMM with regards to kdevops. Those using kdevops in some environemnts
will want to read the last commit.
This work starts off by making the linux-kdevops organization the default
for the source of commits for the kdevops projects. We can now share
efforts, and commits. The last commit will contain more details as
to the motivation for this.
Luis Chamberlain (4):
workflows/Kconfig: be consistent when enabling fstests or blktests
kdevops: move generic kdevops variables to its own file
playbooks: add a common playbook a git reset task for kdevops
kdevops: make linux-kdevops the default tree
kconfigs/workflows/Kconfig | 6 ++++
kconfigs/workflows/Kconfig.shared | 2 +-
playbooks/common.yml | 4 +++
playbooks/roles/common/README.md | 38 ++++++++++++++++++++
playbooks/roles/common/defaults/main.yml | 7 ++++
playbooks/roles/common/tasks/main.yml | 23 ++++++++++++
workflows/Makefile | 33 +----------------
workflows/common/Makefile | 46 ++++++++++++++++++++++++
8 files changed, 126 insertions(+), 33 deletions(-)
create mode 100644 playbooks/common.yml
create mode 100644 playbooks/roles/common/README.md
create mode 100644 playbooks/roles/common/defaults/main.yml
create mode 100644 playbooks/roles/common/tasks/main.yml
create mode 100644 workflows/common/Makefile
--
2.35.1
next reply other threads:[~2022-05-13 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 19:38 Luis Chamberlain [this message]
2022-05-13 19:38 ` [PATCH 1/4] workflows/Kconfig: be consistent when enabling fstests or blktests Luis Chamberlain
2022-05-14 2:21 ` Bart Van Assche
2022-05-15 15:10 ` Luis Chamberlain
2022-05-13 19:38 ` [PATCH 2/4] kdevops: move generic kdevops variables to its own file Luis Chamberlain
2022-05-13 19:38 ` [PATCH 3/4] playbooks: add a common playbook a git reset task for kdevops Luis Chamberlain
2022-05-20 14:44 ` Pankaj Raghav
2022-05-23 17:38 ` Luis Chamberlain
2022-05-13 19:38 ` [PATCH 4/4] kdevops: make linux-kdevops the default tree Luis Chamberlain
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=20220513193831.4136212-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=jake@lwn.net \
--cc=jmeneghi@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pankydev8@gmail.com \
--cc=patches@lists.linux.dev \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).