From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jilin Yuan <yuanjilin@cdjrlc.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH] intel/ixgbe:fix repeated words in comments
Date: Thu, 30 Jun 2022 14:03:14 -0700 [thread overview]
Message-ID: <5590231e-3b1d-643f-deec-e966a734d926@intel.com> (raw)
In-Reply-To: <20220629142952.18664-1-yuanjilin@cdjrlc.com>
On 6/29/2022 7:29 AM, Jilin Yuan wrote:
> Delete the redundant word 'for'.
> Delete the redundant word 'the'.
There are already pending fixes for this [1] [2]. All the still
applicable fixes/patches have been applied.
Thanks,
Tony
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 2 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> index 77c2e70b0860..23b7e1d9652e 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> @@ -5161,7 +5161,7 @@ static int ixgbe_hpbthresh(struct ixgbe_adapter *adapter, int pb)
> }
>
> /**
> - * ixgbe_lpbthresh - calculate low water mark for for flow control
> + * ixgbe_lpbthresh - calculate low water mark for flow control
> *
> * @adapter: board private structure to calculate for
> * @pb: packet buffer to calculate
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c
> index e4b50c7781ff..35c2b9b8bd19 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c
> @@ -1737,7 +1737,7 @@ static s32 ixgbe_setup_sfi_x550a(struct ixgbe_hw *hw, ixgbe_link_speed *speed)
> * @speed: link speed
> * @autoneg_wait_to_complete: unused
> *
> - * Configure the the integrated PHY for native SFP support.
> + * Configure the integrated PHY for native SFP support.
> */
> static s32
> ixgbe_setup_mac_link_sfp_n(struct ixgbe_hw *hw, ixgbe_link_speed speed,
> @@ -1786,7 +1786,7 @@ ixgbe_setup_mac_link_sfp_n(struct ixgbe_hw *hw, ixgbe_link_speed speed,
> * @speed: link speed
> * @autoneg_wait_to_complete: unused
> *
> - * Configure the the integrated PHY for SFP support.
> + * Configure the integrated PHY for SFP support.
> */
> static s32
> ixgbe_setup_mac_link_sfp_x550a(struct ixgbe_hw *hw, ixgbe_link_speed speed,
[1]
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220621082554.52380-1-jiangjian@cdjrlc.com/
[2]
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220623104919.49600-1-jiangjian@cdjrlc.com/
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-06-30 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:29 [Intel-wired-lan] [PATCH] intel/ixgbe:fix repeated words in comments Jilin Yuan
2022-06-30 21:03 ` Tony Nguyen [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=5590231e-3b1d-643f-deec-e966a734d926@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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