From: Guenter Roeck <linux@roeck-us.net>
To: Colin King <colin.king@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: vpd: fix spelling mistake "partion" -> "partition"
Date: Tue, 11 Sep 2018 21:58:48 -0700 [thread overview]
Message-ID: <50220bc9-326f-7a93-fecb-9b67fbac98b9@roeck-us.net> (raw)
In-Reply-To: <20180911165858.3015-1-colin.king@canonical.com>
On 09/11/2018 09:58 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in comment
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Interesting - drivers/firmware/google/ does not have a maintainer.
Greg - is it correct to assume that you are the de-facto maintainer ?
Guenter
> ---
> drivers/firmware/google/vpd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/google/vpd.c b/drivers/firmware/google/vpd.c
> index 1aa67bb5d8c0..c0c0b4e4e281 100644
> --- a/drivers/firmware/google/vpd.c
> +++ b/drivers/firmware/google/vpd.c
> @@ -198,7 +198,7 @@ static int vpd_section_init(const char *name, struct vpd_section *sec,
>
> sec->name = name;
>
> - /* We want to export the raw partion with name ${name}_raw */
> + /* We want to export the raw partition with name ${name}_raw */
> sec->raw_name = kasprintf(GFP_KERNEL, "%s_raw", name);
> if (!sec->raw_name) {
> err = -ENOMEM;
>
next prev parent reply other threads:[~2018-09-12 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 16:58 [PATCH] firmware: vpd: fix spelling mistake "partion" -> "partition" Colin King
2018-09-12 4:58 ` Guenter Roeck [this message]
2018-09-12 5:24 ` Greg Kroah-Hartman
2018-09-12 21:10 ` Guenter Roeck
2018-09-13 12:55 ` Greg Kroah-Hartman
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=50220bc9-326f-7a93-fecb-9b67fbac98b9@roeck-us.net \
--to=linux@roeck-us.net \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).