From: Carlos Maiolino <cmaiolino@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] [LSF/MM ATTEND] XFS reflink, rmap and CoW
Date: Thu, 15 Dec 2016 13:30:29 +0100 [thread overview]
Message-ID: <20161215123029.kq2yedcaayzam2f6@eorzea.usersys.redhat.com> (raw)
Hello,
I've spent past (5 year or so) contributing to XFS (mainly), and another FS
development in kernel, and I would like to participate in LSF/MM 2017.
As usual, most of my interest goes into XFS topics. I'm mostly interested in the
topics in $SUBJ, and how we can make it stable as soon as possible.
I am also interested in attend general VFS topics, and Ext4, and help with
things needed along such areas.
Cheers.
P.S. I apologize to be sending it again, but I've messed up the subject tags in
my previous e-mail, so, sending it again to avoid it to get lost.
--
Carlos
next reply other threads:[~2016-12-15 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 12:30 Carlos Maiolino [this message]
2016-12-16 6:57 [LSF/MM TOPIC] [LSF/MM ATTEND] XFS reflink, rmap and CoW Amir Goldstein
2016-12-16 7:55 ` Christoph Hellwig
2016-12-16 10:27 ` Carlos Maiolino
2016-12-19 23:12 ` Dave Chinner
2016-12-19 23:28 ` Darrick J. Wong
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=20161215123029.kq2yedcaayzam2f6@eorzea.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).