From: Jonathan Cameron <jic23@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Haibo Chen <haibo.chen@nxp.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] iio: adc: imx93: Fix spelling mistake "geting" -> "getting"
Date: Sat, 28 Jan 2023 16:22:15 +0000 [thread overview]
Message-ID: <20230128162215.41bb70cb@jic23-huawei> (raw)
In-Reply-To: <20230124100413.684416-1-colin.i.king@gmail.com>
On Tue, 24 Jan 2023 10:04:13 +0000
Colin Ian King <colin.i.king@gmail.com> wrote:
> Thrre is a spelling mistake in a dev_err_probe message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Applied.
Thanks,
Jonathan
> ---
> drivers/iio/adc/imx93_adc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/imx93_adc.c b/drivers/iio/adc/imx93_adc.c
> index d8de8284e13d..a775d2e40567 100644
> --- a/drivers/iio/adc/imx93_adc.c
> +++ b/drivers/iio/adc/imx93_adc.c
> @@ -315,7 +315,7 @@ static int imx93_adc_probe(struct platform_device *pdev)
> adc->regs = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(adc->regs))
> return dev_err_probe(dev, PTR_ERR(adc->regs),
> - "Failed geting ioremap resource\n");
> + "Failed getting ioremap resource\n");
>
> /* The third irq is for ADC conversion usage */
> adc->irq = platform_get_irq(pdev, 2);
prev parent reply other threads:[~2023-01-28 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 10:04 [PATCH][next] iio: adc: imx93: Fix spelling mistake "geting" -> "getting" Colin Ian King
2023-01-28 16:22 ` Jonathan Cameron [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=20230128162215.41bb70cb@jic23-huawei \
--to=jic23@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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