Re: [PATCH net RFC] net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports

[Arınç ÜNAL]

On 2.02.2024 01:59, Vladimir Oltean wrote:
> On Thu, Feb 01, 2024 at 10:13:39PM +0300, Arınç ÜNAL via B4 Relay wrote:
> > base-commit: 4e192be1a225b7b1c4e315a44754312347628859
> > change-id: 20240201-b4-for-net-mt7530-fix-link-local-that-ingress-vlan-filtering-ports-6a2099e7ffb3
> >
> > Best regards,
> > --
> > Arınç ÜNAL <arinc.unal@xxxxxxxxxx>
>
> You sent this patch 3 times. What happened, b4 didn't work so well?

Odd, I've received only a single email of this patch.

Looking at lore.kernel.org, it looks like the b4 web endpoint properly
submitted the patch to the b4-sent mailing list but for some reason changed
the Message-Id before submitting it to the netdev mailing list.

This is the email with what the Message-Id should be, which only exists on
the b4-sent mailing list:

https://lore.kernel.org/all/20240201-b4-for-net-mt7530-fix-link-local-that-ingress-vlan-filtering-ports-v1-1-881c1c96b27f@xxxxxxxxxx/

This is the email with changed Message-Id that was submitted to the netdev
mailing list:

https://lore.kernel.org/all/=%3Futf-8%3Fq%3F=3C20240201-b4-for-net-mt7530-fix-link-local-that-ingr%3F=%20=%3Futf-8%3Fq%3Fess-vlan-filtering-ports-v1-1-881c1c96b27f=40arinc9=2Ecom=3E%3F=/

There're no brackets enclosing the Message-Id. That must be why Gmail
modified it with the SMTPIN_ADDED_BROKEN disclaimer added for you. I can't
come up with a theory as to why you've received it thrice though.

Konstantin, could you take a look at what happened here?

Arınç