From: Luis Chamberlain <mcgrof@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: kdevops@lists.linux.dev,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-cxl@vger.kernel.org
Subject: kdevops BoF at LSFMM
Date: Tue, 7 May 2024 11:44:26 -0700 [thread overview]
Message-ID: <CAB=NE6XyLS1TaAcgzSWa=1pgezRjFoy8nuVtSWSfB8Qsdsx_xQ@mail.gmail.com> (raw)
Dear LPC session leads,
We'd like to gather together and talk about current ongoing
developments / changes on kdevops at LSFMM. Those interested in
automation on complex workflows with kdevops are also welcomed. This
is best addressed informally, but since I see an open slot for at
10:30am for Tuesday, figured I'd check to see if we can snatch it.
BoFs for filesystems are scheduled towards the end of the conference
on Wednesday it seems, so ideally this would just take place then, but
the last BoF for XFS at Linux Plumbers took... 4 hours, and if such
filesystem BoFs take place I suspect each FS developer would also want
to attend their own respective FS BoF... so perhaps best we get a
kdevops BoF out of the way before the respective filesystem BoFs.
Agenda items?
Guestfs migration progress - have we killed vagrant?
Automation on testing filesystem baselines
xarray / maple tree testing and userspace testing
OpenTofu
kdevops-results-archive split
Any others?
Luis
next reply other threads:[~2024-05-07 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 18:44 Luis Chamberlain [this message]
2024-05-07 18:56 ` kdevops BoF at LSFMM Chuck Lever III
2024-05-08 7:45 ` Amir Goldstein
2024-05-08 15:57 ` Luis Chamberlain
2024-05-13 1:58 ` Matthew Wilcox
2024-05-08 17:45 ` Steve French
2024-05-08 17:54 ` Chuck Lever III
2024-05-12 20:20 ` Luis Chamberlain
2024-05-13 13:17 ` Theodore Ts'o
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='CAB=NE6XyLS1TaAcgzSWa=1pgezRjFoy8nuVtSWSfB8Qsdsx_xQ@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).