From: Christina Quast <cquast@hanoverdisplays.com>
To: gregkh@linuxfoundation.org
Cc: trivial@kernel.org, Christina Quast <cquast@hanoverdisplays.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] fs: kernfs: Corrected spelling mistake
Date: Tue, 2 Apr 2019 16:01:46 +0200 [thread overview]
Message-ID: <20190402140146.3429-1-cquast@hanoverdisplays.com> (raw)
In-Reply-To: <20190402130827.GA32338@kroah.com>
flies => files
Signed-off-by: Christina Quast <cquast@hanoverdisplays.com>
---
Changes since v1:
* Added changelog text
include/linux/kernfs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/kernfs.h b/include/linux/kernfs.h
index c8893f663470..e446ab97ee0c 100644
--- a/include/linux/kernfs.h
+++ b/include/linux/kernfs.h
@@ -64,7 +64,7 @@ enum kernfs_root_flag {
KERNFS_ROOT_CREATE_DEACTIVATED = 0x0001,
/*
- * For regular flies, if the opener has CAP_DAC_OVERRIDE, open(2)
+ * For regular files, if the opener has CAP_DAC_OVERRIDE, open(2)
* succeeds regardless of the RW permissions. sysfs had an extra
* layer of enforcement where open(2) fails with -EACCES regardless
* of CAP_DAC_OVERRIDE if the permission doesn't have the
--
2.20.1
next prev parent reply other threads:[~2019-04-02 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:44 [PATCH] fs: kernfs: Corrected spelling mistake Christina Quast
2019-04-02 11:58 ` Mukesh Ojha
2019-04-02 12:00 ` Greg Kroah-Hartman
2019-04-02 12:27 ` [PATCH v2] " Christina Quast
2019-04-02 13:08 ` Greg Kroah-Hartman
2019-04-02 14:01 ` Christina Quast [this message]
2019-04-02 15:45 ` Joe Perches
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=20190402140146.3429-1-cquast@hanoverdisplays.com \
--to=cquast@hanoverdisplays.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).