linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <yuchao0@huawei.com>,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	Al Viro <viro@ZenIV.linux.org.uk>, Chao Yu <chao@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] vfs: hoist {XFS, EXT4}_IOC_{GOING, SHUT}DOWN to the VFS
Date: Thu, 23 Feb 2017 08:57:58 -0800	[thread overview]
Message-ID: <20170223165758.GC5837@birch.djwong.org> (raw)
In-Reply-To: <20170223101518.GA1769@jaegeuk.local>

On Thu, Feb 23, 2017 at 02:15:19AM -0800, Jaegeuk Kim wrote:
> Hello,
> 
> On 02/23, Chao Yu wrote:
> > Hi Darrick,
> > 
> > On 2017/2/23 15:52, Darrick J. Wong wrote:
> > > ext4 and XFS expose the same shutdown ioctl with the same parameters,
> > > so let's hoist the whole mess into the vfs headers.
> > 
> > Could you cover f2fs in this patch since f2fs has already supported SHUTDOWN ioctl?
> 
> It's funny that I submitted a similar patch two years ago along with f2fs
> support.
> 
> https://patchwork.kernel.org/patch/5814991/

Heh, I didn't even realize that.  I'll pull f2fs into the patch shortly.

--D

> 
> Thanks,

      reply	other threads:[~2017-02-23 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  7:52 [PATCH] vfs: hoist {XFS,EXT4}_IOC_{GOING,SHUT}DOWN to the VFS Darrick J. Wong
2017-02-23  8:54 ` Chao Yu
2017-02-23 10:15   ` [f2fs-dev] [PATCH] vfs: hoist {XFS, EXT4}_IOC_{GOING, SHUT}DOWN " Jaegeuk Kim
2017-02-23 16:57     ` Darrick J. Wong [this message]

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=20170223165758.GC5837@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=yuchao0@huawei.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).