From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
linux-kernel@vger.kernel.org,
"Eric Dumazet" <edumazet@google.com>,
erkin.bozoglu@xeront.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
tools@kernel.org, mithat.guner@xeront.com,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Sean Wang" <sean.wang@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>,
linux-mediatek@lists.infradead.org,
"Bartel Eerdekens" <bartel.eerdekens@constell8.be>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
netdev@vger.kernel.org, "Daniel Golle" <daniel@makrotopia.org>,
"Alvin Šipraga" <ALSI@bang-olufsen.dk>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net RFC] net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports
Date: Mon, 5 Feb 2024 15:24:19 -0500 [thread overview]
Message-ID: <20240205-silky-sensible-puffin-8e23ee@lemur> (raw)
In-Reply-To: <1f0e67ba-edd7-4998-bc20-1de86bd53a68@arinc9.com>
On Fri, Feb 02, 2024 at 12:11:37PM +0300, Arınç ÜNAL wrote:
> 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?
Oh, yay, another python email module bug. *sigh* It's not supposed to break
items enclosed in brackets.
I'll see if I can work around it on the submission side of things, but for now
the silly workaround is not to create branch names that are too long (which
results in message-ids that are very long).
-K
WARNING: multiple messages have this Message-ID (diff)
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: "Vladimir Oltean" <olteanv@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"DENG Qingfang" <dqfext@gmail.com>,
"Sean Wang" <sean.wang@mediatek.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Alvin Šipraga" <ALSI@bang-olufsen.dk>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Bartel Eerdekens" <bartel.eerdekens@constell8.be>,
mithat.guner@xeront.com, erkin.bozoglu@xeront.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, tools@kernel.org
Subject: Re: [PATCH net RFC] net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports
Date: Mon, 5 Feb 2024 15:24:19 -0500 [thread overview]
Message-ID: <20240205-silky-sensible-puffin-8e23ee@lemur> (raw)
In-Reply-To: <1f0e67ba-edd7-4998-bc20-1de86bd53a68@arinc9.com>
On Fri, Feb 02, 2024 at 12:11:37PM +0300, Arınç ÜNAL wrote:
> 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?
Oh, yay, another python email module bug. *sigh* It's not supposed to break
items enclosed in brackets.
I'll see if I can work around it on the submission side of things, but for now
the silly workaround is not to create branch names that are too long (which
results in message-ids that are very long).
-K
WARNING: multiple messages have this Message-ID (diff)
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: "Vladimir Oltean" <olteanv@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"DENG Qingfang" <dqfext@gmail.com>,
"Sean Wang" <sean.wang@mediatek.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Alvin Šipraga" <ALSI@bang-olufsen.dk>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Bartel Eerdekens" <bartel.eerdekens@constell8.be>,
mithat.guner@xeront.com, erkin.bozoglu@xeront.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, tools@kernel.org
Subject: Re: [PATCH net RFC] net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports
Date: Mon, 5 Feb 2024 15:24:19 -0500 [thread overview]
Message-ID: <20240205-silky-sensible-puffin-8e23ee@lemur> (raw)
In-Reply-To: <1f0e67ba-edd7-4998-bc20-1de86bd53a68@arinc9.com>
On Fri, Feb 02, 2024 at 12:11:37PM +0300, Arınç ÜNAL wrote:
> 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?
Oh, yay, another python email module bug. *sigh* It's not supposed to break
items enclosed in brackets.
I'll see if I can work around it on the submission side of things, but for now
the silly workaround is not to create branch names that are too long (which
results in message-ids that are very long).
-K
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-05 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65bbf40d.170a0220.a87f4.becdSMTPIN_ADDED_BROKEN@mx.google.com>
2024-02-01 22:59 ` [PATCH net RFC] net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports Vladimir Oltean
2024-02-01 22:59 ` Vladimir Oltean
2024-02-01 22:59 ` Vladimir Oltean
2024-02-02 9:11 ` Arınç ÜNAL
2024-02-02 9:11 ` Arınç ÜNAL
2024-02-02 9:11 ` Arınç ÜNAL
2024-02-05 20:24 ` Konstantin Ryabitsev [this message]
2024-02-05 20:24 ` Konstantin Ryabitsev
2024-02-05 20:24 ` Konstantin Ryabitsev
2024-02-01 23:26 ` Vladimir Oltean
2024-02-01 23:26 ` Vladimir Oltean
2024-02-01 23:26 ` Vladimir Oltean
2024-02-16 1:24 ` Vladimir Oltean
2024-02-16 1:24 ` Vladimir Oltean
2024-02-16 1:24 ` Vladimir Oltean
2024-02-16 10:47 ` Arınç ÜNAL
2024-02-16 10:47 ` Arınç ÜNAL
2024-02-16 10:47 ` Arınç ÜNAL
2024-02-01 19:13 Arınç ÜNAL
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 19:13 Arınç ÜNAL via B4 Relay
2024-02-01 19:13 ` Arınç ÜNAL via B4 Relay
2024-02-01 19:13 ` Arınç ÜNAL via B4 Relay
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=20240205-silky-sensible-puffin-8e23ee@lemur \
--to=konstantin@linuxfoundation.org \
--cc=ALSI@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=bartel.eerdekens@constell8.be \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mithat.guner@xeront.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.com \
--cc=tools@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.