From: Colin King <colin.king@canonical.com>
To: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oleksij Rempel <linux@rempel-privat.de>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][misc-next] misc: cardreader: fix spelling mistake "invailid" -> "invalid"
Date: Thu, 6 Dec 2018 09:19:36 +0000 [thread overview]
Message-ID: <20181206091936.11871-1-colin.king@canonical.com> (raw)
From: Colin Ian King <colin.king@canonical.com>
There are spelling mistakes in a couple of dev_dbg messages, fix these.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
drivers/misc/cardreader/alcor_pci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/cardreader/alcor_pci.c b/drivers/misc/cardreader/alcor_pci.c
index 6872b8e29b4d..bcb10fa4bc3a 100644
--- a/drivers/misc/cardreader/alcor_pci.c
+++ b/drivers/misc/cardreader/alcor_pci.c
@@ -105,7 +105,7 @@ static int alcor_pci_find_cap_offset(struct alcor_pci_priv *priv,
while (1) {
pci_read_config_dword(pci, where, &val32);
if (val32 == 0xffffffff) {
- dev_dbg(priv->dev, "find_cap_offset invailid value %x.\n",
+ dev_dbg(priv->dev, "find_cap_offset invalid value %x.\n",
val32);
return 0;
}
@@ -116,7 +116,7 @@ static int alcor_pci_find_cap_offset(struct alcor_pci_priv *priv,
}
if ((val32 & 0xff00) == 0x00) {
- dev_dbg(priv->dev, "pci_find_cap_offset invailid value %x.\n",
+ dev_dbg(priv->dev, "pci_find_cap_offset invalid value %x.\n",
val32);
break;
}
--
2.19.1
next reply other threads:[~2018-12-06 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:19 Colin King [this message]
2018-12-07 18:04 ` [PATCH][misc-next] misc: cardreader: fix spelling mistake "invailid" -> "invalid" Oleksij Rempel
2018-12-11 9:36 ` Ulf Hansson
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=20181206091936.11871-1-colin.king@canonical.com \
--to=colin.king@canonical.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=ulf.hansson@linaro.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).