From: Paul Moore <paul@paul-moore.com>
To: Pairman Guo <pairmanxlr@gmail.com>
Cc: jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Pairman Guo <pairmanxlr@gmail.com>
Subject: Re: [PATCH] LSM: Fix typos in security/security.c comment headers
Date: Wed, 21 Feb 2024 19:03:34 -0500 [thread overview]
Message-ID: <86532a709c172423ea200c1cabffa9f3@paul-moore.com> (raw)
In-Reply-To: <20240217133504.4534-1-pairmanxlr@gmail.com>
On Feb 17, 2024 Pairman Guo <pairmanxlr@gmail.com> wrote:
>
> This commit fixes several typos in comment headers in security/security.c
> where "Check is" should be "Check if".
>
> Signed-off-by: Pairman Guo <pairmanxlr@gmail.com>
> ---
> security/security.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Merged into lsm/dev, thanks.
--
paul-moore.com
prev parent reply other threads:[~2024-02-22 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 13:35 [PATCH] LSM: Fix typos in security/security.c comment headers Pairman Guo
2024-02-22 0:03 ` Paul Moore [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=86532a709c172423ea200c1cabffa9f3@paul-moore.com \
--to=paul@paul-moore.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pairmanxlr@gmail.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).