[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240214070908.37b49ddf@kernel.org>
Date: Wed, 14 Feb 2024 07:09:08 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: Florian Fainelli <f.fainelli@...il.com>, <davem@...emloft.net>,
<edumazet@...gle.com>, <pabeni@...hat.com>, <lars.povlsen@...rochip.com>,
<Steen.Hegelund@...rochip.com>, <daniel.machon@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, <u.kleine-koenig@...gutronix.de>,
<rmk+kernel@...linux.org.uk>, <vladimir.oltean@....com>,
<jacob.e.keller@...el.com>, <yuehaibing@...wei.com>,
<netdev@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next] net: sparx5: Add spinlock for frame
transmission from CPU
On Wed, 14 Feb 2024 09:14:42 +0100 Horatiu Vultur wrote:
> > Any reason you targeted 'net-next' rather than 'net', as this appears to
> > be clearly a bug fix here?
>
> Yes, it is a bug but it is not something that happens all the
> time and I thought this fits more into the lines of 'This could be a
> problem ...' therefore I had targeted 'net-next'.
> But if you consider that I should target 'net' instead of 'net-next' I
> can do that.
Definitely a bug fix worthy of net, yes, please.
Powered by blists - more mailing lists