From: Adrian Hunter <adrian.hunter@intel.com>
To: Colin King <colin.king@canonical.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"ernest.zhang" <ernest.zhang@bayhubtech.com>
Subject: Re: [PATCH] mmc: sdhci-pci-o2micro: fix spelling mistake "unsupport" -> "unsupported"
Date: Thu, 6 Aug 2020 15:21:11 +0300 [thread overview]
Message-ID: <016404fc-fce8-20f5-da6c-1b7ea936cf5a@intel.com> (raw)
In-Reply-To: <20200806115059.59241-1-colin.king@canonical.com>
+ code author ernest.zhang <ernest.zhang@bayhubtech.com>
On 6/08/20 2:50 pm, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a pr_info message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/mmc/host/sdhci-pci-o2micro.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sdhci-pci-o2micro.c b/drivers/mmc/host/sdhci-pci-o2micro.c
> index fa76748d8929..4eca8d2d0599 100644
> --- a/drivers/mmc/host/sdhci-pci-o2micro.c
> +++ b/drivers/mmc/host/sdhci-pci-o2micro.c
> @@ -469,7 +469,7 @@ static void sdhci_pci_o2_enable_msi(struct sdhci_pci_chip *chip,
>
> ret = pci_find_capability(chip->pdev, PCI_CAP_ID_MSI);
> if (!ret) {
> - pr_info("%s: unsupport msi, use INTx irq\n",
> + pr_info("%s: unsupported msi, use INTx irq\n",
I think the meaning is more like:
MSI is not supported, using INTx IRQ
> mmc_hostname(host->mmc));
> return;
> }
>
next prev parent reply other threads:[~2020-08-06 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 11:50 [PATCH] mmc: sdhci-pci-o2micro: fix spelling mistake "unsupport" -> "unsupported" Colin King
2020-08-06 12:21 ` Adrian Hunter [this message]
2020-08-06 12:32 ` Adrian Hunter
2021-09-24 22:51 [PATCH] mmc: sdhci-pci-o2micro: Fix " Colin King
2021-09-27 5:43 ` Adrian Hunter
2021-09-27 22:32 ` 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=016404fc-fce8-20f5-da6c-1b7ea936cf5a@intel.com \
--to=adrian.hunter@intel.com \
--cc=colin.king@canonical.com \
--cc=ernest.zhang@bayhubtech.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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).