From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: [PATCH] LSM: drop duplicated words in header file comments
Date: Fri, 17 Jul 2020 16:36:40 -0700 [thread overview]
Message-ID: <9299abf4-75e3-6d73-a8b8-c2617208a990@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Drop the doubled words "the" and "and" in comments.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: James Morris <jmorris@namei.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org
---
include/linux/lsm_hook_defs.h | 2 +-
include/linux/lsm_hooks.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20200714.orig/include/linux/lsm_hook_defs.h
+++ linux-next-20200714/include/linux/lsm_hook_defs.h
@@ -15,7 +15,7 @@
*/
/*
- * The macro LSM_HOOK is used to define the data structures required by the
+ * The macro LSM_HOOK is used to define the data structures required by
* the LSM framework using the pattern:
*
* LSM_HOOK(<return_type>, <default_value>, <hook_name>, args...)
--- linux-next-20200714.orig/include/linux/lsm_hooks.h
+++ linux-next-20200714/include/linux/lsm_hooks.h
@@ -822,7 +822,7 @@
* structure. Note that the security field was not added directly to the
* socket structure, but rather, the socket security information is stored
* in the associated inode. Typically, the inode alloc_security hook will
- * allocate and and attach security information to
+ * allocate and attach security information to
* SOCK_INODE(sock)->i_security. This hook may be used to update the
* SOCK_INODE(sock)->i_security field with additional information that
* wasn't available when the inode was allocated.
next reply other threads:[~2020-07-17 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 23:36 Randy Dunlap [this message]
2020-07-18 2:59 ` [PATCH] LSM: drop duplicated words in header file comments Serge E. Hallyn
2020-07-27 18:39 ` James Morris
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=9299abf4-75e3-6d73-a8b8-c2617208a990@infradead.org \
--to=rdunlap@infradead.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
/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).