From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Colin King <colin.king@canonical.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] misc: gehc-achc: Fix spelling mistake "Verfication" -> "Verification"
Date: Mon, 16 Aug 2021 00:00:33 +0200 [thread overview]
Message-ID: <20210815220033.vfz3v356ucmhgb5x@earth.universe> (raw)
In-Reply-To: <20210815214206.47970-1-colin.king@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Hi,
On Sun, Aug 15, 2021 at 10:42:06PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_dbg debug message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
-- Sebastian
> ---
> drivers/misc/gehc-achc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/gehc-achc.c b/drivers/misc/gehc-achc.c
> index 891d9a214454..02f33bc60c56 100644
> --- a/drivers/misc/gehc-achc.c
> +++ b/drivers/misc/gehc-achc.c
> @@ -280,7 +280,7 @@ static int ezport_flash_compare(struct spi_device *spi, u32 address,
> ret = memcmp(payload, buffer + 4 + 1, payload_size);
> if (ret) {
> ret = -EBADMSG;
> - dev_dbg(&spi->dev, "Verfication failure @ %06x", address);
> + dev_dbg(&spi->dev, "Verification failure @ %06x", address);
> print_hex_dump_bytes("fw: ", DUMP_PREFIX_OFFSET, payload, payload_size);
> print_hex_dump_bytes("dev: ", DUMP_PREFIX_OFFSET, buffer + 4, payload_size);
> }
> --
> 2.32.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-08-15 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 21:42 [PATCH][next] misc: gehc-achc: Fix spelling mistake "Verfication" -> "Verification" Colin King
2021-08-15 22:00 ` Sebastian Reichel [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=20210815220033.vfz3v356ucmhgb5x@earth.universe \
--to=sebastian.reichel@collabora.com \
--cc=arnd@arndb.de \
--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).