From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Luis Chamberlain <mcgrof@kernel.org>,
lsf-pc@lists.linux-foundation.org,
xfs <linux-xfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Chandan Babu R <chandan.babu@oracle.com>, Jan Kara <jack@suse.cz>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: [Lsf-pc] XFS BoF at LSFMM
Date: Thu, 9 May 2024 08:59:27 -0700 [thread overview]
Message-ID: <Zjzy34y7aT0B2J77@infradead.org> (raw)
In-Reply-To: <20240509155528.GN360919@frogsfrogsfrogs>
On Thu, May 09, 2024 at 08:55:28AM -0700, Darrick J. Wong wrote:
> Ritesh and Ted and Jan and I were chatting during the ext4 concall just
> now. Could we have a 30 minute iomap bof at 2:30pm followed by the XFS
> bof after that? That would give us some time to chat with hch about
> iomap (and xfs) direction before he has to leave.
Well, I probably need to leave at about 3pm if I don't want to push it
too much.
> Alternately, we could announce a lunchtime discussion group on Monday
> following Ritesh's presentation about iomap. That could fit everyone's
> schedule better? Also everyone's braincaches will likely be warmer.
Sounds way more useful.
next prev parent reply other threads:[~2024-05-09 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 19:41 XFS BoF at LSFMM Luis Chamberlain
2024-05-09 5:01 ` [Lsf-pc] " Amir Goldstein
2024-05-09 5:05 ` Christoph Hellwig
2024-05-09 5:23 ` Amir Goldstein
2024-05-09 15:55 ` Darrick J. Wong
2024-05-09 15:59 ` Christoph Hellwig [this message]
2024-05-09 17:29 ` Amir Goldstein
2024-05-09 17:47 ` Darrick J. Wong
2024-05-13 13:48 ` Theodore Ts'o
2024-05-13 22:33 ` Darrick J. Wong
2024-05-09 9:09 ` Ritesh Harjani
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=Zjzy34y7aT0B2J77@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ritesh.list@gmail.com \
/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).