linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Colin King <colin.king@canonical.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: safesetid: Fix spelling mistake "cant" -> "can't"
Date: Thu, 26 Aug 2021 15:13:50 -0600	[thread overview]
Message-ID: <a7e0507d-7e16-6e40-41eb-66141c1359ca@linuxfoundation.org> (raw)
In-Reply-To: <20210826121445.13062-1-colin.king@canonical.com>

On 8/26/21 6:14 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in an error message. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   tools/testing/selftests/safesetid/safesetid-test.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/safesetid/safesetid-test.c b/tools/testing/selftests/safesetid/safesetid-test.c
> index 0c4d50644c13..4b809c93ba36 100644
> --- a/tools/testing/selftests/safesetid/safesetid-test.c
> +++ b/tools/testing/selftests/safesetid/safesetid-test.c
> @@ -152,7 +152,7 @@ static void write_policies(void)
>   
>   	fd = open(add_whitelist_policy_file, O_WRONLY);
>   	if (fd < 0)
> -		die("cant open add_whitelist_policy file\n");
> +		die("can't open add_whitelist_policy file\n");
>   	written = write(fd, policy_str, strlen(policy_str));
>   	if (written != strlen(policy_str)) {
>   		if (written >= 0) {
> 

Thanks. Queuing this up for Linux 5.15-rc1.

thanks,
-- Shuah

      reply	other threads:[~2021-08-26 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 12:14 [PATCH] selftests: safesetid: Fix spelling mistake "cant" -> "can't" Colin King
2021-08-26 21:13 ` Shuah Khan [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=a7e0507d-7e16-6e40-41eb-66141c1359ca@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).