From: Jakub Kicinski <kuba@kernel.org>
To: Irlanki Sandeep <irlanki.s@samsung.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, edumazet@google.com,
davem@davemloft.net, pabeni@redhat.com, ncardwell@google.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
corbet@lwn.net, linux-kernel@vger.kernel.org, lorenzo@google.com,
maze@google.com, sporeba@google.com, motomuman@google.com,
madhan.raj@samsung.com, srihari.k@samsung.com,
g.pokhra@samsung.com, r.kumawat@samsung.com,
raj.kumars@samsung.com, ts413.lee@samsung.com,
ramyashree.s@samsung.com, daeil2.hwang@samsung.com
Subject: Re: [PATCH net-next v6] tcp: add BPF kfuncs to set per-socket ECN mode and AccECN option
Date: Wed, 7 Oct 2026 17:00:28 -0700 [thread overview]
Message-ID: <20261007170028.318acb6b@kernel.org> (raw)
In-Reply-To: <20261001132759.1076145-1-irlanki.s@samsung.com>
On Thu, 1 Oct 2026 18:57:59 +0530 Irlanki Sandeep wrote:
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
This needs an ACK from TCP maintainers. If you respin please make sure
to drop this tag, this tag is for cases where someone suggested sending
the patch as a whole. Not for changes requested during normal course of
review.
There was a false positive from sparse regarding the use of kfunc,
I kicked off the AI review manually, please check the results here
in an hour or so:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261001132759.1076145-1-irlanki.s@samsung.com
prev parent reply other threads:[~2026-10-08 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261001132701epcas5p2da9b0fa7ca3bcef1ff84a62f255bc573@epcas5p2.samsung.com>
2026-10-01 13:27 ` Irlanki Sandeep
2026-10-08 0:00 ` Jakub Kicinski [this message]
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=20261007170028.318acb6b@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daeil2.hwang@samsung.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=g.pokhra@samsung.com \
--cc=irlanki.s@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=madhan.raj@samsung.com \
--cc=maze@google.com \
--cc=motomuman@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r.kumawat@samsung.com \
--cc=raj.kumars@samsung.com \
--cc=ramyashree.s@samsung.com \
--cc=sporeba@google.com \
--cc=srihari.k@samsung.com \
--cc=ts413.lee@samsung.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
all inboxes | Powered by JetHome®