From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
david@fromorbit.com,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [GIT PULL] xfs: fixes for v4.20-rc6
Date: Wed, 12 Dec 2018 10:16:58 -0800 [thread overview]
Message-ID: <20181212181658.GA24487@magnolia> (raw)
In-Reply-To: <20181211135818.GA29626@infradead.org>
On Tue, Dec 11, 2018 at 05:58:18AM -0800, Christoph Hellwig wrote:
> On Sat, Dec 08, 2018 at 11:24:48AM -0800, Linus Torvalds wrote:
> > Honestly, I really wish you simply wouldn't send me "xfs" fixes that
> > aren't really xfs-specific at all.
> >
> > All the splice patches (and honestly, I feel some of the iomap ones
> > too) that have come in through the xfs tree should have been handled
> > separately as actual VFS patches. Or at least had acks from Al or
> > something.
>
> iomap came in through the XFS tree originally, and has been very much
> maintained in combo, even though we now have another user with gfs.
>
> Maybe we just need to make that official in MAINTAINERS?
Yes, though who should be the official maintainer? You wrote most of
the iomap code; do you want to maintain it yourself? Or have people
funnel them wherever XFS patches go? :)
--D
next prev parent reply other threads:[~2018-12-12 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 16:36 [GIT PULL] xfs: fixes for v4.20-rc6 Darrick J. Wong
2018-12-08 19:24 ` Linus Torvalds
2018-12-11 13:58 ` Christoph Hellwig
2018-12-12 18:16 ` Darrick J. Wong [this message]
2018-12-13 14:25 ` Christoph Hellwig
2018-12-12 18:13 ` Darrick J. Wong
2018-12-08 19:50 ` pr-tracker-bot
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=20181212181658.GA24487@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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