netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Foster <colin.foster@in-advantage.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v3 net-next 0/5] prepare ocelot for external interface control
Date: Sat, 4 Dec 2021 10:23:13 -0800	[thread overview]
Message-ID: <20211204182313.GB1037231@euler> (raw)
In-Reply-To: <20211204182129.1044899-1-colin.foster@in-advantage.com>

On Sat, Dec 04, 2021 at 10:21:24AM -0800, Colin Foster 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
> 
> some are required for SPI
>   net: dsa: ocelot: felix: add interface for custom regmaps
> 
> and some are just to expose code to be shared
>   net: mscc: ocelot: split register definitions to a separate file
>   net: mscc: ocelot: expose ocelot wm functions
> 
> 
> The entirety of this patch set should have essentially no impact on the
> system performance.
> 
> v1 -> v2
>     * Removed the per-device-per-port quirks for Felix. Might be
>     completely unnecessary.
>     * Fixed the renaming issue for vec7514_regs. It includes the
>     Reported-by kernel test robot by way of git b4... If that isn't the
>     right thing to do in this instance, let me know :-)
> 
> v2 -> v3
>     * Fix an include. Thanks Jakub Kicinski!

Oops - I didn't use git b4 to pull in the reviewed by tags. Sending V4
with those changes and this fix. Apologies!

> 
> Colin Foster (5):
>   net: dsa: ocelot: remove unnecessary pci_bar variables
>   net: dsa: ocelot: felix: Remove requirement for PCS in felix devices
>   net: dsa: ocelot: felix: add interface for custom regmaps
>   net: mscc: ocelot: split register definitions to a separate file
>   net: mscc: ocelot: expose ocelot wm functions
> 
>  drivers/net/dsa/ocelot/felix.c             |   6 +-
>  drivers/net/dsa/ocelot/felix.h             |   4 +-
>  drivers/net/dsa/ocelot/felix_vsc9959.c     |  11 +-
>  drivers/net/dsa/ocelot/seville_vsc9953.c   |   1 +
>  drivers/net/ethernet/mscc/Makefile         |   3 +-
>  drivers/net/ethernet/mscc/ocelot_devlink.c |  31 ++
>  drivers/net/ethernet/mscc/ocelot_vsc7514.c | 548 +--------------------
>  drivers/net/ethernet/mscc/vsc7514_regs.c   | 523 ++++++++++++++++++++
>  include/soc/mscc/ocelot.h                  |   5 +
>  include/soc/mscc/vsc7514_regs.h            |  27 +
>  10 files changed, 610 insertions(+), 549 deletions(-)
>  create mode 100644 drivers/net/ethernet/mscc/vsc7514_regs.c
>  create mode 100644 include/soc/mscc/vsc7514_regs.h
> 
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2021-12-04 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 18:21 [PATCH v3 net-next 0/5] prepare ocelot for external interface control Colin Foster
2021-12-04 18:21 ` [PATCH v3 net-next 1/5] net: dsa: ocelot: remove unnecessary pci_bar variables Colin Foster
2021-12-04 18:21 ` [PATCH v3 net-next 2/5] net: dsa: ocelot: felix: Remove requirement for PCS in felix devices Colin Foster
2021-12-04 18:21 ` [PATCH v3 net-next 3/5] net: dsa: ocelot: felix: add interface for custom regmaps Colin Foster
2021-12-04 18:21 ` [PATCH v3 net-next 4/5] net: mscc: ocelot: split register definitions to a separate file Colin Foster
2021-12-04 18:21 ` [PATCH v3 net-next 5/5] net: mscc: ocelot: expose ocelot wm functions Colin Foster
2021-12-04 18:23 ` Colin Foster [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=20211204182313.GB1037231@euler \
    --to=colin.foster@in-advantage.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.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).