linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Filesystem testing and xfstests
Date: Sat, 14 Jan 2017 00:30:00 +0800	[thread overview]
Message-ID: <20170113163000.GA1859@eguan.usersys.redhat.com> (raw)

Hi all,

I would like to attend the filesystem track in LSF/MM this year. I've
been testing filesystems for 6 years, and testing every RC kernel
release for 2 years. I'm mainly focusing on XFS, extN, overlayfs and
btrfs, also keep an eye on NFS and CIFS. I took over the maintainer role
of xfstests from Dave Chinner in June 2016.

I'm interested in everything about filesystem testing. I'm happy to hear
complaints and answer questions about xfstests. I'm also interested in
general fs development topics, which will decide what we're going to
test. I think it's also a good time for me to meet the XFS development
community.

Thanks,
Eryu

                 reply	other threads:[~2017-01-13 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170113163000.GA1859@eguan.usersys.redhat.com \
    --to=eguan@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).