All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org,
	Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
	linux-afs@lists.infradead.org, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] afs: Improvements for v5.8
Date: Fri, 5 Jun 2020 15:02:29 +0100	[thread overview]
Message-ID: <20200605140229.GI23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200605135003.GH23230@ZenIV.linux.org.uk>

On Fri, Jun 05, 2020 at 02:50:03PM +0100, Al Viro wrote:
> On Thu, Jun 04, 2020 at 05:58:19PM +0100, David Howells wrote:
> > Hi Linus,
> > 
> > Is it too late to put in a pull request for AFS changes?  Apologies - I was
> > holding off and hoping that I could get Al to review the changes I made to
> > the core VFS change commit (first in the series) in response to his earlier
> > review comments.  I have an ack for the Ext4 changes made, though.  If you
> > would prefer it to be held off at this point, fair enough.
> > 
> > Note that the series also got rebased to -rc7 to remove the dependency on
> > fix patches that got merged through the net tree.
> 
> FWIW, I can live with fs/inode.c part in its current form

Which is to say,
ACKed-by: Al Viro <viro@zeniv.linux.org.uk> (fs/inode.c part)
I have not checked the AFS part of the series and AFAICS
ext4 one at least doesn't make things any worse there.

  reply	other threads:[~2020-06-05 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 16:58 [GIT PULL] afs: Improvements for v5.8 David Howells
2020-06-05 13:50 ` Al Viro
2020-06-05 14:02   ` Al Viro [this message]
2020-06-05 23:33 ` Linus Torvalds
2020-06-05 23: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=20200605140229.GI23230@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=dhowells@redhat.com \
    --cc=khlebnikov@yandex-team.ru \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.