From: patchwork-bot+netdevbpf@kernel.org
To: Yuya Kusakabe <yuya.kusakabe@gmail.com>
Cc: andrea.mayer@uniroma2.it, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, g.goller@proxmox.com
Subject: Re: [PATCH net-next v5 0/2] seg6: skip route refcounts in seg6local lookups
Date: Thu, 12 Nov 2026 13:40:05 +0000 [thread overview]
Message-ID: <179449080567.2107380.12389973165436502767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109-seg6-lookup-noref-v5-0-96dc6a652c7e@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 09 Nov 2026 09:10:13 +0900 you wrote:
> seg6local looks up the nexthop of its IPv6 and IPv4 behaviors from the
> RCU read-side section of the receive path, yet takes and drops a route
> reference for every packet. Skip the reference, as ip6_route_input()
> and ip_rcv_finish() do.
>
> An LLM coding assistant helped write and test this series.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] seg6: skip the route refcount in seg6local IPv6 lookups
https://git.kernel.org/netdev/net-next/c/dcbda564e19b
- [net-next,v5,2/2] seg6: skip the route refcount in seg6local IPv4 lookups
https://git.kernel.org/netdev/net-next/c/6b290fe547c2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-12 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 0:10 [PATCH net-next v5 0/2] seg6: skip route refcounts in seg6local lookups Yuya Kusakabe
2026-11-09 0:10 ` [PATCH net-next v5 1/2] seg6: skip the route refcount in seg6local IPv6 lookups Yuya Kusakabe
2026-11-09 0:10 ` [PATCH net-next v5 2/2] seg6: skip the route refcount in seg6local IPv4 lookups Yuya Kusakabe
2026-11-10 8:54 ` Hangbin Liu
2026-11-12 13:40 ` patchwork-bot+netdevbpf [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=179449080567.2107380.12389973165436502767.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=g.goller@proxmox.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuya.kusakabe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.