From: Tobias Klauser <tklauser@distanz.ch>
To: Randy Dunlap <rdunlap@xenotime.net>
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 22:02:21 +0200 [thread overview]
Message-ID: <20110706200221.GF8334@distanz.ch> (raw)
In-Reply-To: <20110706090014.d46bbbe3.rdunlap@xenotime.net>
On 2011-07-06 at 18:00:14 +0200, Randy Dunlap <rdunlap@xenotime.net> wrote:
> 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?
I made the patch against linux-next as of 1 July. The commit comes from
Al Viro's vfs-2.6 tree I guess.
> This patch applies to linux-next, right?
Yup, it should. Sorry, I should have mentioned that in the subject.
next prev parent reply other threads:[~2011-07-06 20:02 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
2011-07-06 20:02 ` Tobias Klauser [this message]
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=20110706200221.GF8334@distanz.ch \
--to=tklauser@distanz.ch \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).