Netdev List
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] net: Fix typos
Date: Mon, 28 Jul 2025 08:49:54 -0500	[thread overview]
Message-ID: <20250728134954.GA3227267@bhelgaas> (raw)
In-Reply-To: <08deec62-e20a-4a54-a655-38a0335a74cd@gmail.com>

On Mon, Jul 28, 2025 at 02:19:41PM +0100, Edward Cree wrote:
> On 23/07/2025 21:15, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas <bhelgaas@google.com>
> > 
> > Fix typos in comments and error messages.

> > +++ b/drivers/net/ethernet/sfc/mcdi_pcol.h
> 
> mcdi_pcol.h is automatically generated from an external source (it comes
>  from the firmware development team), these fixes will likely be
>  overwritten next time we pull in updates.  I will try to get them fed
>  back into the upstream sources.

Thanks!  Is there any way to include a note in the generated file
about the fact that it is generated, and maybe a pointer for where to
send corrections?  It looks like others have made the same mistake
before, but maybe those fixes got fed back upstream behind the scenes:

  982a2b5ffdbb ("sfc: fix repeated words in comments")
  ac6bef064f71 ("sfc: Fix spelling mistake "writting" -> "writing"")
  0f5e15583060 ("scripts/spelling.txt: add "an one" pattern and fix typo instances")

> > +++ b/drivers/net/ethernet/sfc/tc_encap_actions.c
> > @@ -442,7 +442,7 @@ static void efx_tc_update_encap(struct efx_nic *efx,
> >  			rule = container_of(acts, struct efx_tc_flow_rule, acts);
> >  			if (rule->fallback)
> >  				fallback = rule->fallback;
> > -			else /* fallback fallback: deliver to PF */
> > +			else /* fallback: deliver to PF */
> >  				fallback = &efx->tc->facts.pf;
> >  			rc = efx_mae_update_rule(efx, fallback->fw_id,
> >  						 rule->fw_id);
> 
> This wording was intentional, not a type: delivery to the PF is the
>  second-layer fallback when there is no fallback action, which makes it
>  the fallback to the fallback.
> I will post a partial revert to change this line back.

Oof, sorry about that!  Adding something about this being a
second-layer fallback, or a default or last resort when there is no
fallback, might help avoid confusion.

Bjorn

      reply	other threads:[~2025-07-28 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 20:15 [PATCH] net: Fix typos Bjorn Helgaas
2025-07-24  5:49 ` Arinzon, David
2025-07-24 15:46   ` Bjorn Helgaas
2025-07-25 16:28 ` Simon Horman
2025-07-25 17:40 ` patchwork-bot+netdevbpf
2025-07-28 13:19 ` Edward Cree
2025-07-28 13:49   ` Bjorn Helgaas [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=20250728134954.GA3227267@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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