All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs pile 3
Date: Sat, 13 Oct 2012 08:51:28 +0100	[thread overview]
Message-ID: <20121013075128.GQ2616@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5079164D.4030307@gmail.com>

On Sat, Oct 13, 2012 at 09:20:45AM +0200, Marco Stornelli wrote:
> Il 13/10/2012 02:20, Al Viro ha scritto:
> >	Stuff from Jeff Layton, mostly.  Sanitizing interplay between
> >audit and namei, removing a lot of insanity from audit_inode() mess
> >and getting things ready for his ESTALE patchset.  Please, pull from
> >the usual place -
> >git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
> >
> 
> Al,
> 
> do you see any problem to apply the patch series "drop vmtruncate"?

It's somewhat pointless on its own...  If you were doing something with
the callers afterwards - sure, it would be make sense, but as it is...

  reply	other threads:[~2012-10-13  7:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-13  0:20 [git pull] vfs pile 3 Al Viro
2012-10-13  7:20 ` Marco Stornelli
2012-10-13  7:51   ` Al Viro [this message]
2012-10-13  7:52     ` Marco Stornelli
2012-10-13 15:48     ` Christoph Hellwig
2012-10-13 16:01       ` Al Viro
2012-10-13 16:04         ` Christoph Hellwig
2012-10-13 17:07           ` Al Viro
2012-10-14  9:59             ` Marco Stornelli
  -- strict thread matches above, loose matches on Subject: below --
2016-08-07  3:46 Al Viro
2016-08-07 14:00 ` Linus Torvalds
2016-12-23  0:03 Al Viro
2016-12-23 11:44 ` Al Viro
2018-06-04  1:12 [git pull] vfs, " Al Viro

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=20121013075128.GQ2616@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.stornelli@gmail.com \
    --cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.