From: Randy Dunlap <rdunlap@xenotime.net>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VFS: Fixup kerneldoc for generic_permission()
Date: Wed, 6 Jul 2011 09:00:14 -0700 [thread overview]
Message-ID: <20110706090014.d46bbbe3.rdunlap@xenotime.net> (raw)
In-Reply-To: <1309520691-17741-1-git-send-email-tklauser@distanz.ch>
On Fri, 1 Jul 2011 13:44:51 +0200 Tobias Klauser wrote:
> The flags parameter went away in
> 5c90c1601f00154f8695951469f25f33579272ed
What git tree is that commit ID in?
This patch applies to linux-next, right?
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> ---
> fs/namei.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index f181e4c..73fc34a 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -213,7 +213,6 @@ other_perms:
> * generic_permission - check for access rights on a Posix-like filesystem
> * @inode: inode to check access rights for
> * @mask: right to check for (%MAY_READ, %MAY_WRITE, %MAY_EXEC)
> - * @flags: IPERM_FLAG_ flags.
> *
> * Used to check for read/write/execute permissions on a file.
> * We use "fsuid" for this, letting us set arbitrary permissions
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-06 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 11:44 [PATCH] VFS: Fixup kerneldoc for generic_permission() Tobias Klauser
2011-07-06 16:00 ` Randy Dunlap [this message]
2011-07-06 20:02 ` Tobias Klauser
2011-07-06 20:04 ` Randy Dunlap
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=20110706090014.d46bbbe3.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tklauser@distanz.ch \
--cc=viro@zeniv.linux.org.uk \
/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).