From: <Conor.Dooley@microchip.com>
To: <wangjianli@cdjrlc.com>, <tsbogend@alpha.franken.de>
Cc: <linux-mips@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips/sgi-ip22: fix repeated words in comments
Date: Sun, 21 Aug 2022 15:07:30 +0000 [thread overview]
Message-ID: <b2b39e6a-ca51-eb10-dbfc-b70b700d8237@microchip.com> (raw)
In-Reply-To: <20220821150246.51164-1-wangjianli@cdjrlc.com>
Hi,
On 21/08/2022 16:02, wangjianli wrote:
> Delete the redundant word 'in'.
The "duplicated" word here is "of" not "in".
However, I would suspect that the second "of" here is actually
meant to be "open firmware" so there is no duplication here.
Thanks,
Conor.
>
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> arch/mips/sgi-ip22/ip22-gio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/sgi-ip22/ip22-gio.c b/arch/mips/sgi-ip22/ip22-gio.c
> index 38d12f417e48..03d96638f957 100644
> --- a/arch/mips/sgi-ip22/ip22-gio.c
> +++ b/arch/mips/sgi-ip22/ip22-gio.c
> @@ -41,7 +41,7 @@ static struct device gio_bus = {
> /**
> * gio_match_device - Tell if an of_device structure has a matching
> * gio_match structure
> - * @ids: array of of device match structures to search in
> + * @ids: array of device match structures to search in
> * @dev: the of device structure to match against
> *
> * Used by a driver to check whether an of_device present in the
next prev parent reply other threads:[~2022-08-21 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 15:02 [PATCH] mips/sgi-ip22: fix repeated words in comments wangjianli
2022-08-21 15:07 ` Conor.Dooley [this message]
2022-08-21 16:23 ` Sergey Shtylyov
2022-08-21 15:06 wangjianli
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=b2b39e6a-ca51-eb10-dbfc-b70b700d8237@microchip.com \
--to=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=wangjianli@cdjrlc.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;
as well as URLs for NNTP newsgroup(s).