linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Weight <russell.h.weight@intel.com>
To: <trix@redhat.com>, <mdf@kernel.org>, <hao.wu@intel.com>,
	<yilun.xu@intel.com>
Cc: <linux-fpga@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fpga: stratix10-soc: cleanup double word in comment
Date: Tue, 14 Dec 2021 08:59:45 -0800	[thread overview]
Message-ID: <6d5f9555-47c5-c84e-a62d-73fbee78a483@intel.com> (raw)
In-Reply-To: <20211214154749.2463147-1-trix@redhat.com>



On 12/14/21 7:47 AM, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> There are two that's in the comment, remove one.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
Reviewed-by: Russ Weight <russell.h.weight@intel.com>

> ---
>  drivers/fpga/stratix10-soc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/fpga/stratix10-soc.c b/drivers/fpga/stratix10-soc.c
> index 357cea58ec98e..862069c95aa3c 100644
> --- a/drivers/fpga/stratix10-soc.c
> +++ b/drivers/fpga/stratix10-soc.c
> @@ -245,7 +245,7 @@ static int s10_send_buf(struct fpga_manager *mgr, const char *buf, size_t count)
>  	int ret;
>  	uint i;
>  
> -	/* get/lock a buffer that that's not being used */
> +	/* get/lock a buffer that is not being used */
>  	for (i = 0; i < NUM_SVC_BUFS; i++)
>  		if (!test_and_set_bit_lock(SVC_BUF_LOCK,
>  					   &priv->svc_bufs[i].lock))


  reply	other threads:[~2021-12-14 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 15:47 [PATCH] fpga: stratix10-soc: cleanup double word in comment trix
2021-12-14 16:59 ` Russ Weight [this message]
2021-12-15  1:02   ` Xu Yilun

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=6d5f9555-47c5-c84e-a62d-73fbee78a483@intel.com \
    --to=russell.h.weight@intel.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.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).