netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: qiangqing.zhang@nxp.com, davem@davemloft.ne, edumazet@google.com,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethernet/freescale:fix repeated words in comments
Date: Thu, 30 Jun 2022 20:04:58 -0700	[thread overview]
Message-ID: <20220630200458.707053ab@kernel.org> (raw)
In-Reply-To: <20220629124656.55575-1-yuanjilin@cdjrlc.com>

On Wed, 29 Jun 2022 20:46:56 +0800 Jilin Yuan wrote:
> -		/* Write the next next compare(not the next according the spec)
> +		/* Write the next compare(not the next according the spec)

This one may be on purpose, given the clarification in the brackets.

      reply	other threads:[~2022-07-01  3:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 12:46 [PATCH] ethernet/freescale:fix repeated words in comments Jilin Yuan
2022-07-01  3:04 ` Jakub Kicinski [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=20220630200458.707053ab@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.ne \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qiangqing.zhang@nxp.com \
    --cc=yuanjilin@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).