[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221201143134.6bb285d8@kernel.org>
Date: Thu, 1 Dec 2022 14:31:34 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Dmitry Safonov <dima@...sta.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Eric Dumazet <edumazet@...gle.com>,
linux-kernel@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>,
Bob Gilligan <gilligan@...sta.com>,
Dmitry Safonov <0x7f454c46@...il.com>,
Francesco Ruggeri <fruggeri@...sta.com>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Jason Baron <jbaron@...mai.com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Salam Noureddine <noureddine@...sta.com>,
Steven Rostedt <rostedt@...dmis.org>, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>
Subject: Re: [PATCH v6 1/5] jump_label: Prevent key->enabled int overflow
On Fri, 25 Nov 2022 14:28:30 +0000 Dmitry Safonov wrote:
> > What is the plan for merging this? I'm assuming it would want to go
> > through the network tree, but as already noted earlier it depends on a
> > patch I have in tip/locking/core.
> >
> > Now I checked, tip/locking/core is *just* that one patch, so it might be
> > possible to merge that branch and this series into the network tree and
> > note that during the pull request to Linus.
>
> I initially thought it has to go through tip trees because of the
> dependence, but as you say it's just one patch.
>
> I was also asked by Jakub on v4 to wait for Eric's Ack/Review, so once I
> get a go from him, I will send all 6 patches for inclusion into -net
> tree, if that will be in time before the merge window.
Looks like we're all set on the networking side (thanks Eric!!)
Should I pull Peter's branch? Or you want to just resent a patch Peter
already queued. A bit of an unusual situation..
Powered by blists - more mailing lists