From: Chuck Lever III <chuck.lever@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] BoF for nfsd
Date: Sun, 16 Apr 2023 16:02:16 +0000 [thread overview]
Message-ID: <16485039-DE04-4E66-AE08-C1663B150DBD@oracle.com> (raw)
In-Reply-To: <CAOQ4uxj8b8gV02ybuBWMu7ppBc9phrd8J_XMK_bwOYb+Z5hxCg@mail.gmail.com>
> On Apr 16, 2023, at 12:20 AM, Amir Goldstein <amir73il@gmail.com> wrote:
>
> On Sat, Apr 15, 2023 at 7:35 PM Chuck Lever III <chuck.lever@oracle.com> wrote:
>>
>>
>>> On Apr 12, 2023, at 2:26 PM, Chuck Lever III <chuck.lever@oracle.com> wrote:
>>
>>> • NFS/NFSD CI (jlayton)
>>
>> Network filesystems have special requirements for CI.
>> Jeff has been working on shaping kdevops to work for
>> our needs, and the work probably has broader appeal
>> than only to NFS. This could be its own 30-minute session,
>> or maybe we've got most everything worked out already?
>
> Perhaps a guest speaker at Luis's kdevops session?
That's fine with me. I'll give Jeff and Luis the final
word on that.
--
Chuck Lever
prev parent reply other threads:[~2023-04-16 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 18:27 [LSF/MM/BPF TOPIC] BoF for nfsd Chuck Lever III
2023-04-13 9:33 ` Christian Brauner
2023-04-13 13:09 ` Jeff Layton
2023-04-13 17:43 ` Chuck Lever III
2023-04-13 14:05 ` Matthew Wilcox
2023-04-13 14:15 ` Chuck Lever III
2023-04-13 17:54 ` Trond Myklebust
2023-04-15 16:34 ` Chuck Lever III
2023-04-15 16:57 ` Trond Myklebust
2023-04-16 4:20 ` [Lsf-pc] " Amir Goldstein
2023-04-16 16:02 ` Chuck Lever III [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=16485039-DE04-4E66-AE08-C1663B150DBD@oracle.com \
--to=chuck.lever@oracle.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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