[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240223073802.13d2d3d8@kernel.org>
Date: Fri, 23 Feb 2024 07:38:02 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: netdev@...r.kernel.org, deb.chatterjee@...el.com,
anjali.singhai@...el.com, namrata.limaye@...el.com, tom@...anda.io,
mleitner@...hat.com, Mahesh.Shirshyad@....com, Vipin.Jain@....com,
tomasz.osinski@...el.com, jiri@...nulli.us, xiyou.wangcong@...il.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
vladbu@...dia.com, horms@...nel.org, khalidm@...dia.com, toke@...hat.com,
mattyk@...dia.com, daniel@...earbox.net, bpf@...r.kernel.org,
dan.daly@...el.com, andy.fingerhut@...il.com, chris.sommers@...sight.com,
pctammela@...atatu.com, victor@...atatu.com
Subject: Re: [PATCH net-next v11 0/5] Introducing P4TC (series 1)
On Fri, 23 Feb 2024 08:17:23 -0500 Jamal Hadi Salim wrote:
> This is the first patchset of two. In this patch we are only submitting 5
> patches which touch the general TC code given these are trivial. We will be
> posting a second patchset which handles the P4 objects and associated infra
> (which includes 10 patches that we have already been posting to hit the 15
> limit).
Don't use the limit as a justification for questionable tactics :|
If there's still BPF in it, it's not getting merged without BPF
maintainers's acks. So we're going to merge these 5 and then what?
BTW the diffstat at the end of the commit message is from the full set.
Powered by blists - more mailing lists