From: Edward Cree <ecree.xilinx@gmail.com>
To: wangjianli <wangjianli@cdjrlc.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethernet/sfc: fix repeated words in comments
Date: Thu, 8 Sep 2022 17:07:47 +0100 [thread overview]
Message-ID: <30f2488d-9af3-fe8d-6e6f-713a7d38800b@gmail.com> (raw)
In-Reply-To: <20220908124630.24314-1-wangjianli@cdjrlc.com>
On 08/09/2022 13:46, wangjianli wrote:
> Delete the redundant word 'in'.
>
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> drivers/net/ethernet/sfc/bitfield.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/sfc/bitfield.h b/drivers/net/ethernet/sfc/bitfield.h
> index 1f981dfe4bdc..0b502d1c3c9e 100644
> --- a/drivers/net/ethernet/sfc/bitfield.h
> +++ b/drivers/net/ethernet/sfc/bitfield.h
> @@ -117,7 +117,7 @@ typedef union efx_oword {
> *
> * ( element ) << 4
> *
> - * The result will contain the relevant bits filled in in the range
> + * The result will contain the relevant bits filled in the range
> * [0,high-low), with garbage in bits [high-low+1,...).
> */
> #define EFX_EXTRACT_NATIVE(native_element, min, max, low, high) \
>
Nack.
"filled in" is a phrasal verb, so the existing text is correct. Stet.
#ifdef RANT
NGL, getting kinda sick of these bogus comment text 'fixes' from people
who clearly don't have enough mastery of English to copyedit it.
(Previous one from this author was actually wrong too but I didn't catch
it at the time.)
English is a tricksy language, why would someone with a limited
understanding of it think that grammar fixes are the best use of their
time and energy?
I can't help suspecting that this is a box-ticking exercise, where a
certain corporate culture has a standard requirement that engineers
must get X number of Linux / opensource commits in order to get
promoted, and this kind of mindless patch is the easiest way for them
to achieve that.
#endif
-ed
prev parent reply other threads:[~2022-09-08 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:46 wangjianli
2022-09-08 16:07 ` Edward Cree [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=30f2488d-9af3-fe8d-6e6f-713a7d38800b@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®