[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bc8f189c-3f37-b6ec-3422-f14a9cf0b85b@canonical.com>
Date: Tue, 16 Apr 2019 12:56:00 -0700
From: John Johansen <john.johansen@...onical.com>
To: Colin King <colin.king@...onical.com>,
James Morris <jmorris@...ei.org>,
"Serge E . Hallyn" <serge@...lyn.com>,
linux-security-module@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] apparmor: fix spelling mistake "immutible" -> "immutable"
On 4/16/19 7:42 AM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> There is a spelling mistake in an information message string, fix it.
>
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
Acked-by: John Johansen <john.johansen@...onical.com>
I'll pull it into the apparmor tree
> ---
> security/apparmor/policy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/apparmor/policy.c b/security/apparmor/policy.c
> index 71a3e6291478..04f2480e8374 100644
> --- a/security/apparmor/policy.c
> +++ b/security/apparmor/policy.c
> @@ -587,7 +587,7 @@ static int replacement_allowed(struct aa_profile *profile, int noreplace,
> {
> if (profile) {
> if (profile->label.flags & FLAG_IMMUTIBLE) {
> - *info = "cannot replace immutible profile";
> + *info = "cannot replace immutable profile";
> return -EPERM;
> } else if (noreplace) {
> *info = "profile already exists";
>
Powered by blists - more mailing lists