From: Randy Dunlap <rdunlap@infradead.org>
To: trix@redhat.com, broonie@kernel.org, gregkh@linuxfoundation.org,
rafael@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: irq: cleanup comments
Date: Sat, 12 Feb 2022 08:00:54 -0800 [thread overview]
Message-ID: <8ad7556a-cfdc-dae7-da58-89e973ca1179@infradead.org> (raw)
In-Reply-To: <20220212143144.2648689-1-trix@redhat.com>
On 2/12/22 06:31, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> Replace the second 'which' with 'the'.
> Change 'acknowleding' to 'acknowledging'.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/base/regmap/regmap-irq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/regmap/regmap-irq.c b/drivers/base/regmap/regmap-irq.c
> index d5604f497296..81f6356f0589 100644
> --- a/drivers/base/regmap/regmap-irq.c
> +++ b/drivers/base/regmap/regmap-irq.c
> @@ -537,7 +537,7 @@ static irqreturn_t regmap_irq_thread(int irq, void *d)
>
> /*
> * Ignore masked IRQs and ack if we need to; we ack early so
> - * there is no race between handling and acknowleding the
> + * there is no race between handling and acknowledging the
> * interrupt. We assume that typically few of the interrupts
> * will fire simultaneously so don't worry about overhead from
> * doing a write per register.
> @@ -1082,7 +1082,7 @@ EXPORT_SYMBOL_GPL(devm_regmap_add_irq_chip);
> /**
> * devm_regmap_del_irq_chip() - Resource managed regmap_del_irq_chip()
> *
> - * @dev: Device for which which resource was allocated.
> + * @dev: Device for which the resource was allocated.
> * @irq: Primary IRQ for the device.
> * @data: ®map_irq_chip_data allocated by regmap_add_irq_chip().
> *
--
~Randy
next prev parent reply other threads:[~2022-02-12 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 14:31 trix
2022-02-12 16:00 ` Randy Dunlap [this message]
2022-02-14 12:51 ` Mark Brown
2022-02-14 14:56 ` Mark Brown
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=8ad7556a-cfdc-dae7-da58-89e973ca1179@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=trix@redhat.com \
/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
all inboxes | Powered by JetHome®