MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: matthieu.baerts@tessares.net, davem@davemloft.net,
	edumazet@google.com,  kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org,  mptcp@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mptcp: Fix comment typo
Date: Tue, 19 Jul 2022 09:56:12 -0700 (PDT)	[thread overview]
Message-ID: <1414d684-8881-5b2a-4824-e3c4488e862@linux.intel.com> (raw)
In-Reply-To: <20220716044226.43587-1-wangborong@cdjrlc.com>


On Sat, 16 Jul 2022, Jason Wang wrote:

> The double `the' is duplicated in the comment, remove one.
>
> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> ---
> net/mptcp/token.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/mptcp/token.c b/net/mptcp/token.c
> index f52ee7b26aed..68b822691e36 100644
> --- a/net/mptcp/token.c
> +++ b/net/mptcp/token.c
> @@ -288,7 +288,7 @@ EXPORT_SYMBOL_GPL(mptcp_token_get_sock);
>  * token container starting from the specified position, or NULL.
>  *
>  * On successful iteration, the iterator is move to the next position and the

Two more changes are needed in the line above:

move -> moved
the -> then

Thanks for the contribution.

> - * the acquires a reference to the returned socket.
> + * acquires a reference to the returned socket.
>  */
> struct mptcp_sock *mptcp_token_iter_next(const struct net *net, long *s_slot,
> 					 long *s_num)
> -- 
> 2.35.1
>
>

--
Mat Martineau
Intel

      parent reply	other threads:[~2022-07-19 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16  4:42 [PATCH] mptcp: Fix comment typo Jason Wang
2022-07-19 14:44 ` mptcp: Fix comment typo: Tests Results MPTCP CI
2022-07-19 16:56 ` Mat Martineau [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=1414d684-8881-5b2a-4824-e3c4488e862@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wangborong@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