linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
	lars.povlsen@microchip.com, Steen.Hegelund@microchip.com,
	UNGLinuxDriver@microchip.com, richardcochran@gmail.com,
	jensemil.schulzostergaard@microchip.com,
	horatiu.vultur@microchip.com, jacob.e.keller@intel.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v2 0/5] net: lan969x: add FDMA support
Date: Wed, 15 Jan 2025 22:50:35 +0000	[thread overview]
Message-ID: <173698143504.903583.7524014147804199820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250113-sparx5-lan969x-switch-driver-5-v2-0-c468f02fd623@microchip.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 13 Jan 2025 20:36:04 +0100 you wrote:
> == Description:
> 
> This series is the last of a multi-part series, that prepares and adds
> support for the new lan969x switch driver.
> 
> The upstreaming efforts has been split into multiple series:
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] net: sparx5: enable FDMA on lan969x
    https://git.kernel.org/netdev/net-next/c/4a7d78c27806
  - [net-next,v2,2/5] net: sparx5: split sparx5_fdma_{start(),stop()}
    https://git.kernel.org/netdev/net-next/c/b91dcb237c69
  - [net-next,v2,3/5] net: sparx5: activate FDMA tx in start()
    https://git.kernel.org/netdev/net-next/c/cded2e0f1b0d
  - [net-next,v2,4/5] net: sparx5: ops out certain FDMA functions
    https://git.kernel.org/netdev/net-next/c/56143c52a342
  - [net-next,v2,5/5] net: lan969x: add FDMA implementation
    https://git.kernel.org/netdev/net-next/c/d84ad2c0d80c

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




      parent reply	other threads:[~2025-01-15 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 19:36 [PATCH net-next v2 0/5] net: lan969x: add FDMA support Daniel Machon
2025-01-13 19:36 ` [PATCH net-next v2 1/5] net: sparx5: enable FDMA on lan969x Daniel Machon
2025-01-13 19:36 ` [PATCH net-next v2 2/5] net: sparx5: split sparx5_fdma_{start(),stop()} Daniel Machon
2025-01-13 19:36 ` [PATCH net-next v2 3/5] net: sparx5: activate FDMA tx in start() Daniel Machon
2025-01-13 19:36 ` [PATCH net-next v2 4/5] net: sparx5: ops out certain FDMA functions Daniel Machon
2025-01-13 19:36 ` [PATCH net-next v2 5/5] net: lan969x: add FDMA implementation Daniel Machon
2025-01-15 22:50 ` 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=173698143504.903583.7524014147804199820.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jensemil.schulzostergaard@microchip.com \
    --cc=kuba@kernel.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.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).