[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CO6PR18MB38730422BDF0FF5310117B05B0C10@CO6PR18MB3873.namprd18.prod.outlook.com>
Date: Sun, 20 Dec 2020 10:49:58 +0000
From: Stefan Chulski <stefanc@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
"davem@...emloft.net" <davem@...emloft.net>,
Nadav Haklai <nadavh@...vell.com>,
Yan Markman <ymarkman@...vell.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"andrew@...n.ch" <andrew@...n.ch>,
"rmk+kernel@...linux.org.uk" <rmk+kernel@...linux.org.uk>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH net v3] net: mvpp2: Fix GoP port 3 Networking
Complex Control configurations
> External Email
>
> ----------------------------------------------------------------------
> On Thu, 17 Dec 2020 14:37:28 +0200 stefanc@...vell.com wrote:
> > From: Stefan Chulski <stefanc@...vell.com>
> >
> > During GoP port 2 Networking Complex Control mode of operation
> > configurations, also GoP port 3 mode of operation was wrongly set.
> > Patch removes these configurations.
> > GENCONF_CTRL0_PORTX naming also fixed.
>
> Testing the stable backport it looks like this addition change will be
> problematic. Not to mention it goes against the "fixes should be minimal" rule.
>
> Could you please send just a one liner which removes the offending ORing in
> of the bad bit?
>
> We can do the rename soon after in net-next, the trees are merged pretty
> much every week so it won't be a long wait.
I would repost with single line change.
Regards,
Stefan.
Powered by blists - more mailing lists