All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@bombadil.infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: jmorris@namei.org, serge@hallyn.com,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] device_cgroup: A typo fix
Date: Sat, 20 Mar 2021 22:49:30 -0700 (PDT)	[thread overview]
Message-ID: <1f7b653a-3e15-eea4-9128-402b2ed28b@bombadil.infradead.org> (raw)
In-Reply-To: <20210321040941.31973-1-unixbhaskar@gmail.com>



On Sun, 21 Mar 2021, Bhaskar Chowdhury wrote:

>
> s/acessed/accessed/
>
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

although I still don't care for the $Subject.


> ---
> Changes from V1:
>  Getting rid of unwanted comment delimeter addition
>  Subject line missed propper commit subject labeling
>
> security/device_cgroup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index 04375df52fc9..30b3083276df 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -409,7 +409,7 @@ static bool verify_new_ex(struct dev_cgroup *dev_cgroup,
> 		} else {
> 			/*
> 			 * new exception in the child will add more devices
> -			 * that can be acessed, so it can't match any of
> +			 * that can be accessed, so it can't match any of
> 			 * parent's exceptions, even slightly
> 			 */
> 			match = match_exception_partial(&dev_cgroup->exceptions,
> --
> 2.20.1
>
>

      reply	other threads:[~2021-03-21  5:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21  4:09 [PATCH V2] device_cgroup: A typo fix Bhaskar Chowdhury
2021-03-21  5:49 ` Randy Dunlap [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=1f7b653a-3e15-eea4-9128-402b2ed28b@bombadil.infradead.org \
    --to=rdunlap@bombadil.infradead.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=unixbhaskar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.