From: Tero Kristo <t-kristo@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: ti/ti_sci_protocol.h: drop a duplicated word + clarify
Date: Mon, 20 Jul 2020 10:28:32 +0300 [thread overview]
Message-ID: <54d19b9e-2439-eed2-ff8e-82a1acb4ff33@ti.com> (raw)
In-Reply-To: <20200719003145.21100-1-rdunlap@infradead.org>
On 19/07/2020 03:31, Randy Dunlap wrote:
> Drop the repeated word "an" in a comment.
> Insert "and" between "source" and "destination" as is done a few
> lines earlier.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Santosh Shilimkar <ssantosh@kernel.org>
> Cc: Lokesh Vutla <lokeshvutla@ti.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: linux-arm-kernel@lists.infradead.org
Reviewed-by: Tero Kristo <t-kristo@ti.com>
> ---
> include/linux/soc/ti/ti_sci_protocol.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20200717.orig/include/linux/soc/ti/ti_sci_protocol.h
> +++ linux-next-20200717/include/linux/soc/ti/ti_sci_protocol.h
> @@ -226,8 +226,8 @@ struct ti_sci_rm_core_ops {
> * and destination
> * @set_event_map: Set an Event based peripheral irq to Interrupt
> * Aggregator.
> - * @free_irq: Free an an IRQ route between the requested source
> - * destination.
> + * @free_irq: Free an IRQ route between the requested source
> + * and destination.
> * @free_event_map: Free an event based peripheral irq to Interrupt
> * Aggregator.
> */
>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2020-07-20 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 0:31 Randy Dunlap
2020-07-20 7:28 ` Tero Kristo [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=54d19b9e-2439-eed2-ff8e-82a1acb4ff33@ti.com \
--to=t-kristo@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=rdunlap@infradead.org \
--cc=ssantosh@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
all inboxes | Powered by JetHome®