linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
	alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
	andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
	davem@davemloft.net, kuba@kernel.org, linux@armlinux.org.uk
Subject: Re: [PATCH v5 net-next 0/4] prepare ocelot for external interface control
Date: Wed, 08 Dec 2021 06:00:09 +0000	[thread overview]
Message-ID: <163894320994.16121.3519671067437027854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211207170030.1406601-1-colin.foster@in-advantage.com>

Hello:

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

On Tue,  7 Dec 2021 09:00:26 -0800 you wrote:
> This patch set is derived from an attempt to include external control
> for a VSC751[1234] chip via SPI. That patch set has grown large and is
> getting unwieldy for reviewers and the developers... me.
> 
> I'm breaking out the changes from that patch set. Some are trivial
>   net: dsa: ocelot: remove unnecessary pci_bar variables
>   net: dsa: ocelot: felix: Remove requirement for PCS in felix devices
> 
> [...]

Here is the summary with links:
  - [v5,net-next,1/4] net: dsa: ocelot: remove unnecessary pci_bar variables
    https://git.kernel.org/netdev/net-next/c/c99104840a95
  - [v5,net-next,2/4] net: dsa: ocelot: felix: Remove requirement for PCS in felix devices
    https://git.kernel.org/netdev/net-next/c/49af6a7620c5
  - [v5,net-next,3/4] net: dsa: ocelot: felix: add interface for custom regmaps
    https://git.kernel.org/netdev/net-next/c/242bd0c10bbd
  - [v5,net-next,4/4] net: mscc: ocelot: split register definitions to a separate file
    https://git.kernel.org/netdev/net-next/c/32ecd22ba60b

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



      parent reply	other threads:[~2021-12-08  6:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 17:00 [PATCH v5 net-next 0/4] prepare ocelot for external interface control Colin Foster
2021-12-07 17:00 ` [PATCH v5 net-next 1/4] net: dsa: ocelot: remove unnecessary pci_bar variables Colin Foster
2021-12-07 17:00 ` [PATCH v5 net-next 2/4] net: dsa: ocelot: felix: Remove requirement for PCS in felix devices Colin Foster
2021-12-08  0:41   ` Florian Fainelli
2021-12-07 17:00 ` [PATCH v5 net-next 3/4] net: dsa: ocelot: felix: add interface for custom regmaps Colin Foster
2021-12-08  0:42   ` Florian Fainelli
2021-12-07 17:00 ` [PATCH v5 net-next 4/4] net: mscc: ocelot: split register definitions to a separate file Colin Foster
2021-12-08  0:44   ` Florian Fainelli
2021-12-08  6:00 ` 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=163894320994.16121.3519671067437027854.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=colin.foster@in-advantage.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.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).