From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Miklos Szeredi <miklos@szeredi•hu>
Subject: linux-next: suspect commits in the vfs tree
Date: Thu, 12 May 2016 07:31:53 +1000 [thread overview]
Message-ID: <20160512073153.4132026e@canb.auug.org.au> (raw)
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).
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-05-11 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:31 Stephen Rothwell [this message]
2016-05-11 22:23 ` linux-next: suspect commits in the vfs tree 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=20160512073153.4132026e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miklos@szeredi$(echo .)hu \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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