linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Dave Chinner <david@fromorbit.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v2] iomap: take responsibility for the filesystem iomap code
Date: Thu, 20 Dec 2018 19:07:45 +0000	[thread overview]
Message-ID: <20181220190745.GW2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20181220190401.GD27208@magnolia>

On Thu, Dec 20, 2018 at 11:04:01AM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> XFS is the primary user of the filesystem iomap code, so we (the XFS
> community, specifically) will explicitly take responsibility for its
> maintenance.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

ACK from me, for what it's worth - you guys brought it in, you appear
to actively maintain it, so it's your headac^Wresponsibility.

  reply	other threads:[~2018-12-20 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  5:36 [RFC PATCH] iomap: take responsibility for the filesystem iomap code Darrick J. Wong
2018-12-20  7:08 ` Christoph Hellwig
2018-12-20  7:27 ` Amir Goldstein
2018-12-20 19:04 ` [PATCH v2] " Darrick J. Wong
2018-12-20 19:07   ` Al Viro [this message]
2018-12-21 22:05   ` Dave Chinner
2018-12-24  0:37 ` [PATCH v3] " Darrick J. Wong
2018-12-27  8:08   ` Christoph Hellwig

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=20181220190745.GW2217@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.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).