From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>, <netdev@vger.kernel.org>,
<deb.chatterjee@intel.com>, <anjali.singhai@intel.com>,
<namrata.limaye@intel.com>, <tom@sipanda.io>,
<mleitner@redhat.com>, <Mahesh.Shirshyad@amd.com>,
<Vipin.Jain@amd.com>, <tomasz.osinski@intel.com>,
<jiri@resnulli.us>, <xiyou.wangcong@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<vladbu@nvidia.com>, <horms@kernel.org>, <khalidm@nvidia.com>,
<toke@redhat.com>, <mattyk@nvidia.com>, <daniel@iogearbox.net>,
<bpf@vger.kernel.org>, <dan.daly@intel.com>,
<andy.fingerhut@gmail.com>, <chris.sommers@keysight.com>,
<pctammela@mojatatu.com>, <victor@mojatatu.com>
Subject: Re: [PATCH net-next v11 0/5] Introducing P4TC (series 1)
Date: Fri, 23 Feb 2024 17:07:47 +0100 [thread overview]
Message-ID: <ZdjC002yiviuAqh1@boxer> (raw)
In-Reply-To: <20240223073802.13d2d3d8@kernel.org>
On Fri, Feb 23, 2024 at 07:38:02AM -0800, Jakub Kicinski wrote:
> 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.
...and it is followed by the current one, but that old scary diffstat
sould better go away ;)
>
next prev parent reply other threads:[~2024-02-23 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 13:17 [PATCH net-next v11 0/5] Introducing P4TC (series 1) Jamal Hadi Salim
2024-02-23 13:17 ` [PATCH net-next v11 1/5] net: sched: act_api: Introduce P4 actions list Jamal Hadi Salim
2024-02-23 13:17 ` [PATCH net-next v11 2/5] net/sched: act_api: increase action kind string length Jamal Hadi Salim
2024-02-23 13:17 ` [PATCH net-next v11 3/5] net/sched: act_api: Update tc_action_ops to account for P4 actions Jamal Hadi Salim
2024-02-23 13:17 ` [PATCH net-next v11 4/5] net/sched: act_api: add struct p4tc_action_ops as a parameter to lookup callback Jamal Hadi Salim
2024-02-23 13:17 ` [PATCH net-next v11 5/5] net: sched: act_api: Add support for preallocated P4 action instances Jamal Hadi Salim
2024-02-23 15:38 ` [PATCH net-next v11 0/5] Introducing P4TC (series 1) Jakub Kicinski
2024-02-23 16:07 ` Maciej Fijalkowski [this message]
2024-02-23 16:54 ` Jamal Hadi Salim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdjC002yiviuAqh1@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=Mahesh.Shirshyad@amd.com \
--cc=Vipin.Jain@amd.com \
--cc=andy.fingerhut@gmail.com \
--cc=anjali.singhai@intel.com \
--cc=bpf@vger.kernel.org \
--cc=chris.sommers@keysight.com \
--cc=dan.daly@intel.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=deb.chatterjee@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=khalidm@nvidia.com \
--cc=kuba@kernel.org \
--cc=mattyk@nvidia.com \
--cc=mleitner@redhat.com \
--cc=namrata.limaye@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=toke@redhat.com \
--cc=tom@sipanda.io \
--cc=tomasz.osinski@intel.com \
--cc=victor@mojatatu.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).