From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
George McCollister <george.mccollister@gmail.com>
Subject: [PATCH v2 net-next 0/3] DSA cross-chip notifier cleanup
Date: Wed, 5 Jan 2022 15:18:10 +0200 [thread overview]
Message-ID: <20220105131813.2647558-1-vladimir.oltean@nxp.com> (raw)
This series deletes the no-op cross-chip notifier support for MRP and
HSR, features which were introduced relatively recently and did not get
full review at the time. The new code is functionally equivalent, but
simpler.
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: George McCollister <george.mccollister@gmail.com>
Vladimir Oltean (3):
net: dsa: fix incorrect function pointer check for MRP ring roles
net: dsa: remove cross-chip support for MRP
net: dsa: remove cross-chip support for HSR
net/dsa/dsa_priv.h | 27 --------------
net/dsa/port.c | 73 +++++++++++++++++---------------------
net/dsa/switch.c | 88 ----------------------------------------------
3 files changed, 33 insertions(+), 155 deletions(-)
--
2.25.1
next reply other threads:[~2022-01-05 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 13:18 Vladimir Oltean [this message]
2022-01-05 13:18 ` [PATCH v2 net-next 1/3] net: dsa: fix incorrect function pointer check for MRP ring roles Vladimir Oltean
2022-01-05 13:18 ` [PATCH v2 net-next 2/3] net: dsa: remove cross-chip support for MRP Vladimir Oltean
2022-01-05 13:18 ` [PATCH v2 net-next 3/3] net: dsa: remove cross-chip support for HSR Vladimir Oltean
2022-01-05 15:20 ` [PATCH v2 net-next 0/3] DSA cross-chip notifier cleanup patchwork-bot+netdevbpf
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=20220105131813.2647558-1-vladimir.oltean@nxp.com \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.