From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>, <andrew@lunn.ch>,
Vladimir Oltean <vladimir.oltean@nxp.com>, <jiri@resnulli.us>,
<ivecera@redhat.com>, <davem@davemloft.net>, <roopa@nvidia.com>,
<nikolay@nvidia.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>
Subject: Re: [PATCH net-next v2 0/4] bridge: mrp: Extend br_mrp_switchdev_*
Date: Tue, 2 Feb 2021 21:06:49 +0100 [thread overview]
Message-ID: <20210202200649.mc7vpgltoqxf2oni@soft-dev3.localdomain> (raw)
In-Reply-To: <20210202115032.6affffdc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
The 02/02/2021 11:50, Jakub Kicinski wrote:
>
> On Tue, 2 Feb 2021 08:40:02 +0100 Rasmus Villemoes wrote:
> > On 30/01/2021 04.01, Jakub Kicinski wrote:
> > > On Wed, 27 Jan 2021 21:52:37 +0100 Horatiu Vultur wrote:
> > >> This patch series extends MRP switchdev to allow the SW to have a better
> > >> understanding if the HW can implement the MRP functionality or it needs
> > >> to help the HW to run it. There are 3 cases:
> >
> > >> v2:
> > >> - fix typos in comments and in commit messages
> > >> - remove some of the comments
> > >> - move repeated code in helper function
> > >> - fix issue when deleting a node when sw_backup was true
> > >
> > > Folks who were involved in previous MRP conversations - does this look
> > > good to you? Anyone planning to test?
> >
> > I am planning to test these, but it's unlikely I'll get around to it
> > this week unfortunately.
>
> Horatiu are you okay with deferring the series until Rasmus validates?
> Given none of this HW is upstream now (AFAIU) this is an awkward set
> to handle. Having a confirmation from Rasmus would make us a little bit
> more comfortable.
It is perfectly fine for me to wait for Rasmus to validate this series.
Also I have started to have a look how to implement the switchdev calls
for Ocelot driver. I might have something by the end of the week, but
lets see.
--
/Horatiu
next prev parent reply other threads:[~2021-02-02 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 20:52 [PATCH net-next v2 0/4] bridge: mrp: Extend br_mrp_switchdev_* Horatiu Vultur
2021-01-27 20:52 ` [PATCH net-next v2 1/4] switchdev: mrp: Extend ring_role_mrp and in_role_mrp Horatiu Vultur
2021-01-27 20:52 ` [PATCH net-next v2 2/4] bridge: mrp: Add 'enum br_mrp_hw_support' Horatiu Vultur
2021-01-27 20:52 ` [PATCH net-next v2 3/4] bridge: mrp: Extend br_mrp_switchdev to detect better the errors Horatiu Vultur
2021-01-27 20:52 ` [PATCH net-next v2 4/4] bridge: mrp: Update br_mrp to use new return values of br_mrp_switchdev Horatiu Vultur
2021-01-30 3:01 ` [PATCH net-next v2 0/4] bridge: mrp: Extend br_mrp_switchdev_* Jakub Kicinski
2021-02-02 7:40 ` Rasmus Villemoes
2021-02-02 19:50 ` Jakub Kicinski
2021-02-02 20:06 ` Horatiu Vultur [this message]
2021-02-02 20:49 ` Jakub Kicinski
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=20210202200649.mc7vpgltoqxf2oni@soft-dev3.localdomain \
--to=horatiu.vultur@microchip.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=roopa@nvidia.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