[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250214140311.43f58050@kernel.org>
Date: Fri, 14 Feb 2025 14:03:11 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Peter Zijlstra
<peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Will Deacon
<will@...nel.org>, Boqun Feng <boqun.feng@...il.com>, Waiman Long
<longman@...hat.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Simon Horman
<horms@...nel.org>, Hayes Wang <hayeswang@...ltek.com>,
linux-usb@...r.kernel.org, netdev@...r.kernel.org, Breno Leitao
<leitao@...ian.org>
Subject: Re: [PATCH 1/2] net: Assert proper context while calling
napi_schedule()
On Thu, 13 Feb 2025 21:39:51 +0100 Frederic Weisbecker wrote:
> Le Wed, Feb 12, 2025 at 07:48:20PM -0800, Jakub Kicinski a écrit :
> > On Wed, 12 Feb 2025 18:43:28 +0100 Frederic Weisbecker wrote:
> > Please post the fixes for net, and then the warning in net-next.
> > So that we have some time to fix the uncovered warnings before
> > users are broadly exposed to them.
>
> How do I define the patch target? Is it just about patch prefix?
Yes, --subject-prefix="PATCH net" for fixes
--subject-prefix="PATCH net-next" for -next stuff
But even that isn't really a super hard requirement. My main ask
was to post patch 2, then wait for it to propagate (we merge the
trees every Thu afternoon) then post patch 1.
Sorry for the delay.
Powered by blists - more mailing lists