From: Seth Arnold <seth.arnold@canonical.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, apparmor@lists.ubuntu.com
Subject: Re: [apparmor] [PATCH] security: apparmor: file.h: delete duplicated word
Date: Wed, 22 Jul 2020 20:35:14 +0000 [thread overview]
Message-ID: <20200722203514.GB84486@millbarge> (raw)
In-Reply-To: <20200719180835.24658-1-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
On Sun, Jul 19, 2020 at 11:08:35AM -0700, Randy Dunlap wrote:
> Delete the doubled word "then" in a comment.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: John Johansen <john.johansen@canonical.com>
> Cc: apparmor@lists.ubuntu.com
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Thanks
> ---
> security/apparmor/include/file.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20200717.orig/security/apparmor/include/file.h
> +++ linux-next-20200717/security/apparmor/include/file.h
> @@ -167,7 +167,7 @@ int aa_audit_file(struct aa_profile *pro
> * @perms: permission table indexed by the matched state accept entry of @dfa
> * @trans: transition table for indexed by named x transitions
> *
> - * File permission are determined by matching a path against @dfa and then
> + * File permission are determined by matching a path against @dfa and
> * then using the value of the accept entry for the matching state as
> * an index into @perms. If a named exec transition is required it is
> * looked up in the transition table.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-07-22 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 18:08 [PATCH] security: apparmor: file.h: delete duplicated word Randy Dunlap
2020-07-22 20:35 ` Seth Arnold [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=20200722203514.GB84486@millbarge \
--to=seth.arnold@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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