From: patchwork-bot+netdevbpf@kernel.org
To: Peter Enderborg <Peter.Enderborg@axis.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
daniel@makrotopia.org, peterend@axis.com
Subject: Re: [PATCH net-next v2] if_ether.h: Clarify ethertype validity for gsw1xx dsa
Date: Fri, 28 Nov 2025 02:20:24 +0000 [thread overview]
Message-ID: <176429642402.114872.17810001754416637371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251126135405.58119-1-Peter.Enderborg@axis.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Nov 2025 14:54:06 +0100 you wrote:
> From: Peter Enderborg <peterend@axis.com>
>
> This 0x88C3 is registered to Infineon Technologies Corporate Research ST
> and are used by MaxLinear.
> Infineon made a spin off called Lantiq.
> Lantiq was acquired by Intel
> MaxLinear acquired Intels Connected Home division.
>
> [...]
Here is the summary with links:
- [net-next,v2] if_ether.h: Clarify ethertype validity for gsw1xx dsa
https://git.kernel.org/netdev/net-next/c/6557cae0a2a1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-28 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 13:59 [PATCH for net-next] if_ether.h: Clarify ethertype validity for gsw1xx dsa Peter Enderborg
2025-11-14 14:06 ` Daniel Golle
2025-11-15 20:41 ` Andrew Lunn
2025-11-17 9:02 ` Peter Enderborg
2025-11-17 13:28 ` Andrew Lunn
2025-11-17 14:59 ` Peter Enderborg
2025-11-17 15:16 ` Andrew Lunn
2025-11-26 13:54 ` [PATCH net-next v2] " Peter Enderborg
2025-11-26 14:32 ` Andrew Lunn
2025-11-28 2:20 ` patchwork-bot+netdevbpf [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=176429642402.114872.17810001754416637371.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Peter.Enderborg@axis.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterend@axis.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;
as well as URLs for NNTP newsgroup(s).