[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200624113156.hsutqewk4xntmkld@soft-dev3.localdomain>
Date: Wed, 24 Jun 2020 13:31:56 +0200
From: Horatiu Vultur <horatiu.vultur@...rochip.com>
To: David Miller <davem@...emloft.net>
CC: <nikolay@...ulusnetworks.com>, <roopa@...ulusnetworks.com>,
<kuba@...nel.org>, <linux-kernel@...r.kernel.org>,
<bridge@...ts.linux-foundation.org>, <netdev@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH net v2 0/2] bridge: mrp: Update MRP_PORT_ROLE
The 06/23/2020 14:38, David Miller wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Horatiu Vultur <horatiu.vultur@...rochip.com>
> Date: Tue, 23 Jun 2020 11:05:39 +0200
>
> > This patch series does the following:
> > - fixes the enum br_mrp_port_role_type. It removes the port role none(0x2)
> > because this is in conflict with the standard. The standard defines the
> > interconnect port role as value 0x2.
> > - adds checks regarding current defined port roles: primary(0x0) and
> > secondary(0x1).
> >
> > v2:
> > - add the validation code when setting the port role.
>
> Series applied, thank you.
Thanks. Will these patches be applied also on net-next?
Because if I start now to add support for the interconnect port, these
patches are needed on net-next. Or do I need to add these patches to the
patch series for the interconnect port?
What is the correct way of doing this?
--
/Horatiu
Powered by blists - more mailing lists