[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoMk=1dsi1C02si9MV_E-wX5hu01bi5yTfyMmL9i2FLys1g@mail.gmail.com>
Date: Tue, 12 Nov 2024 07:23:29 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Alexandre Ferrieux <alexandre.ferrieux@...il.com>, Eric Dumazet <edumazet@...gle.com>,
Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko <jiri@...nulli.us>,
alexandre.ferrieux@...nge.com,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH net v6] net: sched: cls_u32: Fix u32's systematic failure
to free IDR entries for hnodes.
On Mon, Nov 11, 2024 at 1:26 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Sat, 9 Nov 2024 07:50:53 -0500 Jamal Hadi Salim wrote:
> > Please split the test into a separate patch targeting net-next.
>
> Separate patch - okay, but why are you asking people to send the tests
> to net-next? These sort of requests lead people to try to run
> linux-next tests on stable trees.
AFAIK, those are the rules.
The test case is not a fix therefore cant go to -net.
You wait until the fix shows up in net-next then you push the test
case into net-next.
I should have clarified to Alexandre the "wait until the fix shows up
in net-next" part.
cheers,
jamal
Powered by blists - more mailing lists