From: Paul Moore <paul@paul-moore.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
selinux@vger.kernel.org, James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] security: selinux: delete repeated words in comments
Date: Fri, 7 Aug 2020 14:09:56 -0400 [thread overview]
Message-ID: <CAHC9VhQW-8pem59QHQctx9UNhMNLEAjNwDiOU1ODz9wX5B_tdQ@mail.gmail.com> (raw)
In-Reply-To: <20200807165134.3913-1-rdunlap@infradead.org>
On Fri, Aug 7, 2020 at 12:51 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Drop a repeated word in comments.
> {open, is, then}
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Stephen Smalley <stephen.smalley.work@gmail.com>
> Cc: Eric Paris <eparis@parisplace.org>
> Cc: selinux@vger.kernel.org
> Cc: James Morris <jmorris@namei.org>
> Cc: "Serge E. Hallyn" <serge@hallyn.com>
> Cc: linux-security-module@vger.kernel.org
> ---
> security/selinux/hooks.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
This obviously looks fine, but it will need to wait until after the
merge window closes. I'll send another reply once it is merged.
> --- linux-next-20200731.orig/security/selinux/hooks.c
> +++ linux-next-20200731/security/selinux/hooks.c
> @@ -1978,7 +1978,7 @@ static inline u32 file_to_av(struct file
> }
>
> /*
> - * Convert a file to an access vector and include the correct open
> + * Convert a file to an access vector and include the correct
> * open permission.
> */
> static inline u32 open_file_to_av(struct file *file)
> @@ -4444,7 +4444,7 @@ static int selinux_skb_peerlbl_sid(struc
> *
> * If @skb_sid is valid then the user:role:type information from @sk_sid is
> * combined with the MLS information from @skb_sid in order to create
> - * @conn_sid. If @skb_sid is not valid then then @conn_sid is simply a copy
> + * @conn_sid. If @skb_sid is not valid then @conn_sid is simply a copy
> * of @sk_sid. Returns zero on success, negative values on failure.
> *
> */
> @@ -5314,7 +5314,7 @@ static int selinux_sctp_bind_connect(str
>
> /* As selinux_sctp_bind_connect() is called by the
> * SCTP protocol layer, the socket is already locked,
> - * therefore selinux_netlbl_socket_connect_locked() is
> + * therefore selinux_netlbl_socket_connect_locked()
> * is called here. The situations handled are:
> * sctp_connectx(3), sctp_sendmsg(3), sendmsg(2),
> * whenever a new IP address is added or when a new
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2020-08-07 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 16:51 [PATCH] security: selinux: delete repeated words in comments Randy Dunlap
2020-08-07 18:09 ` Paul Moore [this message]
2020-08-24 13:07 ` Paul Moore
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=CAHC9VhQW-8pem59QHQctx9UNhMNLEAjNwDiOU1ODz9wX5B_tdQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.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).