From: Tom Rix <trix@redhat.com>
To: Navin Sankar Velliangiri <navin@linumiz.com>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
"mdf@kernel.org" <mdf@kernel.org>
Subject: Re: [PATCH] fpga: fpga-bridge: removed repeated word
Date: Fri, 28 May 2021 08:17:08 -0700 [thread overview]
Message-ID: <6f1cda18-ce61-ea6c-423f-263612d748e8@redhat.com> (raw)
In-Reply-To: <20210528150557.22970-1-navin@linumiz.com>
On 5/28/21 8:05 AM, Navin Sankar Velliangiri wrote:
> Removed repeated word and.
> Reported by checkpatch.
>
> Signed-off-by: Navin Sankar Velliangiri <navin@linumiz.com>
> ---
> drivers/fpga/fpga-bridge.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c
> index e9266b2a357f..9ada1126faf7 100644
> --- a/drivers/fpga/fpga-bridge.c
> +++ b/drivers/fpga/fpga-bridge.c
> @@ -228,7 +228,7 @@ EXPORT_SYMBOL_GPL(fpga_bridges_put);
> * @info: fpga image specific information
> * @bridge_list: list of FPGA bridges
> *
> - * Get an exclusive reference to the bridge and and it to the list.
> + * Get an exclusive reference to the bridge and it to the list.
> *
> * Return 0 for success, error code from of_fpga_bridge_get() othewise.
> */
> @@ -258,7 +258,7 @@ EXPORT_SYMBOL_GPL(of_fpga_bridge_get_to_list);
> * @info: fpga image specific information
> * @bridge_list: list of FPGA bridges
> *
> - * Get an exclusive reference to the bridge and and it to the list.
> + * Get an exclusive reference to the bridge and it to the list.
Looks good.
Reviewed-by: Tom Rix <trix@redhat.com>
Moritz,
This patch and my spelling cleanup are low risk, can we get these into
fpga-next ?
https://lore.kernel.org/linux-fpga/20210527200900.GA875457@mail.gmail.com/
Tom
> *
> * Return 0 for success, error code from fpga_bridge_get() othewise.
> */
next prev parent reply other threads:[~2021-05-28 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 15:05 [PATCH] fpga: fpga-bridge: removed repeated word Navin Sankar Velliangiri
2021-05-28 15:17 ` Tom Rix [this message]
2021-05-28 22:14 ` Moritz Fischer
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=6f1cda18-ce61-ea6c-423f-263612d748e8@redhat.com \
--to=trix@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=navin@linumiz.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).