From: Masami Hiramatsu <mhiramat@kernel.org>
To: Colin King <colin.king@canonical.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] tools: bootconfig: fix spelling mistake "faile" -> "failed"
Date: Thu, 16 Jan 2020 19:02:39 +0900 [thread overview]
Message-ID: <20200116190239.9b318b2faa14465ece414f16@kernel.org> (raw)
In-Reply-To: <20200116092206.52192-1-colin.king@canonical.com>
Hi Colin,
On Thu, 16 Jan 2020 09:22:06 +0000
Colin King <colin.king@canonical.com> wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are two spelling mistakes in printf statements, fix these.
Good catch!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks!
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> tools/bootconfig/main.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/bootconfig/main.c b/tools/bootconfig/main.c
> index b8f174fd2a0a..91c9a5c0c499 100644
> --- a/tools/bootconfig/main.c
> +++ b/tools/bootconfig/main.c
> @@ -140,7 +140,7 @@ int load_xbc_from_initrd(int fd, char **buf)
> return 0;
>
> if (lseek(fd, -8, SEEK_END) < 0) {
> - printf("Faile to lseek: %d\n", -errno);
> + printf("Failed to lseek: %d\n", -errno);
> return -errno;
> }
>
> @@ -155,7 +155,7 @@ int load_xbc_from_initrd(int fd, char **buf)
> return 0;
>
> if (lseek(fd, stat.st_size - 8 - size, SEEK_SET) < 0) {
> - printf("Faile to lseek: %d\n", -errno);
> + printf("Failed to lseek: %d\n", -errno);
> return -errno;
> }
>
> --
> 2.24.0
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-01-16 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 9:22 [PATCH][next] tools: bootconfig: fix spelling mistake "faile" -> "failed" Colin King
2020-01-16 10:02 ` Masami Hiramatsu [this message]
2020-01-20 3:04 ` Masami Hiramatsu
2020-01-21 23:10 ` Steven Rostedt
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=20200116190239.9b318b2faa14465ece414f16@kernel.org \
--to=mhiramat@kernel.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.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