From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: linux-next: suspect commits in the vfs tree
Date: Wed, 11 May 2016 23:23:31 +0100 [thread overview]
Message-ID: <20160511222331.GQ2694@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160512073153.4132026e@canb.auug.org.au>
On Thu, May 12, 2016 at 07:31:53AM +1000, Stephen Rothwell wrote:
> Hi Al,
>
> I noticed these commits in today's vfs tree:
>
> 38b78a5f1858 ovl: ignore permissions on underlying lookup
> 3c9fe8cdff1b vfs: add lookup_hash() helper
> 9409e22acdfc vfs: rename: check backing inode being equal
> 54d5ca871e72 vfs: add vfs_select_inode() helper
>
> They are all committed by you , but have no Signed-off-by from you.
>
> These commits are also in the overlayfs tree (since that has been rebased
> on top of them).
That's a branch from Miklos with a fixup folded into the first of four;
I didn't want to bother with extra roundtrip and folded the fixup in-place.
Hadn't noticed the lack of S-o-b until after I'd pushed, TBH...
prev parent reply other threads:[~2016-05-11 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:31 linux-next: suspect commits in the vfs tree Stephen Rothwell
2016-05-11 22:23 ` Al Viro [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=20160511222331.GQ2694@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sfr@canb.auug.org.au \
/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).