From: <Claudiu.Beznea@microchip.com>
To: <dengshaomin@cdjrlc.com>, <linus.walleij@linaro.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <Ludovic.Desroches@microchip.com>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <jgross@suse.com>,
<sstabellini@kernel.org>, <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH] pinctrl: at91: Fix double word in comments
Date: Thu, 25 Aug 2022 05:42:42 +0000 [thread overview]
Message-ID: <cbf2164c-332d-9787-31d0-3c5f8ff53d93@microchip.com> (raw)
In-Reply-To: <20220825014921.6135-1-dengshaomin@cdjrlc.com>
On 25.08.2022 04:49, Shaomin Deng wrote:
> [Some people who received this message don't often get email from dengshaomin@cdjrlc.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Delete the rebundant word "the" in comments.
>
> Signed-off-by: Shaomin Deng <dengshaomin@cdjrlc.com>
> ---
> drivers/pinctrl/pinctrl-at91.c | 2 +-
> drivers/xen/xen-pciback/pciback_ops.c | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
> index d91a010e65f5..f1234e719e58 100644
> --- a/drivers/pinctrl/pinctrl-at91.c
> +++ b/drivers/pinctrl/pinctrl-at91.c
> @@ -1748,7 +1748,7 @@ static int at91_gpio_of_irq_setup(struct platform_device *pdev,
> writel_relaxed(~0, at91_gpio->regbase + PIO_IDR);
>
> /*
> - * Let the generic code handle this edge IRQ, the the chained
> + * Let the generic code handle this edge IRQ, the chained
> * handler will perform the actual work of handling the parent
> * interrupt.
> */
> diff --git a/drivers/xen/xen-pciback/pciback_ops.c b/drivers/xen/xen-pciback/pciback_ops.c
> index e38b43b5065e..52da75bf8485 100644
> --- a/drivers/xen/xen-pciback/pciback_ops.c
> +++ b/drivers/xen/xen-pciback/pciback_ops.c
> @@ -160,7 +160,8 @@ int xen_pcibk_enable_msi(struct xen_pcibk_device *pdev,
> }
>
> /* The value the guest needs is actually the IDT vector, not the
> - * local domain's IRQ number. */
> + * local domain's IRQ number.
> + */
This should go in a different patch.
>
> op->value = dev->irq ? xen_pirq_from_irq(dev->irq) : 0;
>
> --
> 2.35.1
>
prev parent reply other threads:[~2022-08-25 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 1:49 [PATCH] pinctrl: at91: Fix double word in comments Shaomin Deng
2022-08-25 5:42 ` Claudiu.Beznea [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=cbf2164c-332d-9787-31d0-3c5f8ff53d93@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=dengshaomin@cdjrlc.com \
--cc=jgross@suse.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@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).