public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Charles Perry <charles.perry@microchip.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, nicolas.ferre@microchip.com,
	claudiu.beznea@tuxon.dev, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint
Date: Tue, 17 Mar 2026 12:40:18 +0000	[thread overview]
Message-ID: <177375121878.3601019.14341430328492652693.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260313140610.3681752-1-charles.perry@microchip.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 13 Mar 2026 07:06:07 -0700 you wrote:
> Hello,
> 
> This series add basic support for Microchip "PIC64-HPSC" and "PIC64HX"
> Ethernet endpoint. Both SoCs contain 4 GEM IP with support for
> MII/RGMII/SGMII/USXGMII at rates of 10M to 10G. Only RGMII and SGMII at a
> rate of 1G is tested for now. Each GEM IP has 8 priority queues and the
> revision register reads 0x220c010e.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/3] dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc
    https://git.kernel.org/netdev/net-next/c/63e9d434ddc8
  - [net-next,v3,2/3] net: macb: add safeguards for jumbo frame larger than 10240
    https://git.kernel.org/netdev/net-next/c/363a99af19a7
  - [net-next,v3,3/3] net: macb: add support for Microchip pic64hpsc ethernet endpoint
    https://git.kernel.org/netdev/net-next/c/f45797fe02df

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-17 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 14:06 [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint Charles Perry
2026-03-13 14:06 ` [PATCH net-next v3 1/3] dt-bindings: net: cdns,macb: add a compatible for Microchip pic64hpsc Charles Perry
2026-03-17 15:31   ` Théo Lebrun
2026-03-13 14:06 ` [PATCH net-next v3 2/3] net: macb: add safeguards for jumbo frame larger than 10240 Charles Perry
2026-03-16 17:21   ` Théo Lebrun
2026-03-16 18:26     ` Charles Perry
2026-03-17 12:29       ` Paolo Abeni
2026-03-17 15:32         ` Théo Lebrun
2026-03-13 14:06 ` [PATCH net-next v3 3/3] net: macb: add support for Microchip pic64hpsc ethernet endpoint Charles Perry
2026-03-17 15:32   ` Théo Lebrun
2026-03-16 17:28 ` [PATCH net-next v3 0/3] Initial support for PIC64-HPSC/HX Ethernet endpoint Théo Lebrun
2026-03-16 18:47   ` Charles Perry
2026-03-17 12:31   ` Paolo Abeni
2026-03-17 12:40 ` 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=177375121878.3601019.14341430328492652693.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=charles.perry@microchip.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pabeni@redhat.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox