Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: robert.hodaszi@digi.com
Cc: patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew@lunn.ch, claudiu.manoil@nxp.com,
	alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic
Date: Thu, 19 Dec 2024 17:07:43 +0200	[thread overview]
Message-ID: <20241219150743.rhw2nv3fysplysrf@skbuf> (raw)
In-Reply-To: <173457903151.1807897.16925032481407031771.git-patchwork-notify@kernel.org>

On Thu, Dec 19, 2024 at 03:30:31AM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
> 
> This patch was applied to netdev/net.git (main)
> by Jakub Kicinski <kuba@kernel.org>:
> 
> On Mon, 16 Dec 2024 15:50:59 +0200 you wrote:
> > Robert Hodaszi reports that locally terminated traffic towards
> > VLAN-unaware bridge ports is broken with ocelot-8021q. He is describing
> > the same symptoms as for commit 1f9fc48fd302 ("net: dsa: sja1105: fix
> > reception from VLAN-unaware bridges").
> > 
> > For context, the set merged as "VLAN fixes for Ocelot driver":
> > https://lore.kernel.org/netdev/20240815000707.2006121-1-vladimir.oltean@nxp.com/
> > 
> > [...]
> 
> Here is the summary with links:
>   - [net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic
>     https://git.kernel.org/netdev/net/c/16f027cd40ee
> 
> You are awesome, thank you!
> -- 
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
> 
>

This is on me, sorry. I should have marked this patch as "changes requested",
(https://lore.kernel.org/netdev/49d10bde-6257-4cc0-abaf-3bffb3a812c0@digi.com/)
but I had other urgent priorities. I will send the requested removal of
the duplicate br_vlan_get_proto() calls in net-next once the main branch
gets reintegrated into it.

To Robert, and not meant as an accusation at all, because I could have
done something about it too, earlier: when you have comments for an
already-posted patch, please make them _on that patch_ and not somewhere else.

      reply	other threads:[~2024-12-19 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 13:50 [PATCH net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic Vladimir Oltean
2024-12-19  3:30 ` patchwork-bot+netdevbpf
2024-12-19 15:07   ` Vladimir Oltean [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=20241219150743.rhw2nv3fysplysrf@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=robert.hodaszi@digi.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