[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y3dJN/vgBmFfV+dL@DEN-LT-70577>
Date: Fri, 18 Nov 2022 08:47:31 +0000
From: <Daniel.Machon@...rochip.com>
To: <andrew@...n.ch>
CC: <luwei32@...wei.com>, <davem@...emloft.net>, <edumazet@...gle.com>,
<kuba@...nel.org>, <pabeni@...hat.com>,
<Lars.Povlsen@...rochip.com>, <Steen.Hegelund@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [patch net-next] net: microchip: sparx5: remove useless code in
sparx5_qos_init()
Den Thu, Nov 17, 2022 at 09:14:38PM +0100 skrev Andrew Lunn:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> > sparx5_qos_init() will be expanded in later patch series, as new QoS
> > features require new initializations - so this is actually somewhat
> > intentional.
>
> When do you expect such patches to land?
Most likely sometime in the next window.
>
> If it going to be soon, we can keep the code as it is. If it is going
> to be a while, the bots are going to keep finding this and what to
> remove it.
I see. If bots will be bugging us regularly, then it might just be best
to let the patch through.
>
> Andrew
/ Daniel
Powered by blists - more mailing lists