linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] vfs patches for 4.11
Date: Thu, 2 Mar 2017 09:57:36 +0000	[thread overview]
Message-ID: <20170302095736.GW29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOQ4uxjE0COiGABRwA1Zz-kOAwYjUfGdJitT8AhgHBU2r8sBpA@mail.gmail.com>

On Thu, Mar 02, 2017 at 10:32:08AM +0200, Amir Goldstein wrote:
> On Mon, Feb 20, 2017 at 7:17 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Mon, Feb 20, 2017 at 05:19:00PM +0100, Miklos Szeredi wrote:
> >> Hi Al,
> >>
> >> Please pull from:
> >>
> >>   git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git for-viro
> >>
> >> Amir Goldstein (4):
> >>       vfs: create vfs helper vfs_tmpfile()
> >>       vfs: deny fallocate() on directory
> >>       vfs: deny copy_file_range() for non regular files
> >>       vfs: wrap write f_ops with file_{start,end}_write()
> >
> > The last one could have a better summary, but anyway - pulled.
> 
> Al,
> 
> Please excuse my impatience, but do you plan to send these out to
> Linus for 4.11?

Yes.  As the matter of fact, it will be one of the pull requests in today's
pile.

  reply	other threads:[~2017-03-02  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 16:19 [GIT PULL] vfs patches for 4.11 Miklos Szeredi
2017-02-20 17:17 ` Al Viro
2017-03-02  8:32   ` Amir Goldstein
2017-03-02  9:57     ` Al Viro [this message]
2017-03-03  8:12       ` Amir Goldstein

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=20170302095736.GW29622@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).