From: tytso@mit.edu
To: Jakub Sitnicki <jsitnicki@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ext4: acl: remove unneeded include of linux/capability.h
Date: Mon, 24 Mar 2014 19:00:00 -0400 [thread overview]
Message-ID: <20140324230000.GB13535@thunk.org> (raw)
In-Reply-To: <1395645732-26569-1-git-send-email-jsitnicki@gmail.com>
On Mon, Mar 24, 2014 at 08:22:12AM +0100, Jakub Sitnicki wrote:
> acl.c has not been (directly) using the interface defined by
> linux/capability.h header since commit 3bd858ab1c451725c07a
> ("Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid
> check"). Remove it.
>
> Signed-off-by: Jakub Sitnicki <jsitnicki@gmail.com>
Thanks, applied.
- Ted
prev parent reply other threads:[~2014-03-24 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 7:22 [PATCH 2/2] ext4: acl: remove unneeded include of linux/capability.h Jakub Sitnicki
2014-03-24 12:20 ` Jakub Sitnicki
2014-03-24 23:00 ` tytso [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=20140324230000.GB13535@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jsitnicki@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).