All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, dsahern@kernel.org, idosch@nvidia.com,
	horms@kernel.org, kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/5] neighbour: Misc follow-ups on per-netns neigh_table series.
Date: Tue, 20 Oct 2026 19:00:09 +0000	[thread overview]
Message-ID: <179252280902.159319.14955125563828408722.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013205816.1642597-1-kuniyu@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 13 Oct 2026 20:57:27 +0000 you wrote:
> Patch 1 updates the switchdev doc, s/arp_tbl/arp_table(net)/.
> 
> Patch 2 updates a selftest for per-netns sysctl knobs, though this
> is not an actual issue since the test does not hit gc_thresh by
> default.
> 
> Patches 3 ~ 5 are based on a suggestion by Ido Schimmel to make
> neigh_periodic_work() and neigh_managed_work() CPU-friendly:
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/5] Documentation: networking: switchdev: Replace arp_tbl with arp_table(net).
    https://git.kernel.org/netdev/net-next/c/3e2ca51e7e35
  - [v2,net-next,2/5] selftests: netfilter: Set gc_thresh[123] for gw netns in nft_nat_zones.sh.
    https://git.kernel.org/netdev/net-next/c/2335e48461f2
  - [v2,net-next,3/5] neighbour: Schedule neigh_managed_work only when needed.
    https://git.kernel.org/netdev/net-next/c/8854b0e247ae
  - [v2,net-next,4/5] neighbour: Floor INTERVAL_PROBE_TIME_MS at 1000.
    https://git.kernel.org/netdev/net-next/c/7a71343ba1a6
  - [v2,net-next,5/5] neighbour: Floor neigh_periodic_work() interval at 1s.
    https://git.kernel.org/netdev/net-next/c/ccd0742641dc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-20 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 20:57 [PATCH v2 net-next 0/5] neighbour: Misc follow-ups on per-netns neigh_table series Kuniyuki Iwashima
2026-10-13 20:57 ` [PATCH v2 net-next 1/5] Documentation: networking: switchdev: Replace arp_tbl with arp_table(net) Kuniyuki Iwashima
2026-10-13 20:57 ` [PATCH v2 net-next 2/5] selftests: netfilter: Set gc_thresh[123] for gw netns in nft_nat_zones.sh Kuniyuki Iwashima
2026-10-13 20:57 ` [PATCH v2 net-next 3/5] neighbour: Schedule neigh_managed_work only when needed Kuniyuki Iwashima
2026-10-14  7:00   ` Ido Schimmel
2026-10-13 20:57 ` [PATCH v2 net-next 4/5] neighbour: Floor INTERVAL_PROBE_TIME_MS at 1000 Kuniyuki Iwashima
2026-10-14  7:01   ` Ido Schimmel
2026-10-13 20:57 ` [PATCH v2 net-next 5/5] neighbour: Floor neigh_periodic_work() interval at 1s Kuniyuki Iwashima
2026-10-14  7:01   ` Ido Schimmel
2026-10-20 19:00 ` 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=179252280902.159319.14955125563828408722.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.