From: Aurelien Aptel <aaptel@suse.com>
To: linux-fsdevel@vger.kernel.org
Cc: Aurelien Aptel <aaptel@suse.com>, trivial@kernel.org
Subject: [PATCH 1/1] fs/inode.c: spelling in inode_owner_or_capable doc
Date: Fri, 21 Apr 2017 13:37:58 +0200 [thread overview]
Message-ID: <20170421113758.16274-1-aaptel@suse.com> (raw)
CC: trivial@kernel.org
Signed-off-by: Aurelien Aptel <aaptel@suse.com>
---
fs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/inode.c b/fs/inode.c
index 88110fd0b282..6d9a10afb79d 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -2014,7 +2014,7 @@ EXPORT_SYMBOL(inode_init_owner);
* inode_owner_or_capable - check current task permissions to inode
* @inode: inode being checked
*
- * Return true if current either has CAP_FOWNER in a namespace with the
+ * Return true if current task has either CAP_FOWNER in a namespace with the
* inode owner uid mapped, or owns the file.
*/
bool inode_owner_or_capable(const struct inode *inode)
--
2.12.0
next reply other threads:[~2017-04-21 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 11:37 Aurelien Aptel [this message]
2017-04-21 12:21 ` [PATCH 1/1] fs/inode.c: spelling in inode_owner_or_capable doc Matthew Wilcox
2017-04-21 13:36 ` Aurélien Aptel
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=20170421113758.16274-1-aaptel@suse.com \
--to=aaptel@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trivial@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).