All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jack Ma <jack4it@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
	stephen@networkplumber.org, kuba@kernel.org
Subject: Re: [PATCH iproute2-next v2 0/2] ip nexthop: support fdb destination port
Date: Mon, 03 Aug 2026 18:10:15 +0000	[thread overview]
Message-ID: <178578061514.2763391.9165782985549600808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723-b4-vxlan-fdb-port-iproute2-v2-0-9012ac01b49e@gmail.com>

Hello:

This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Thu, 23 Jul 2026 01:25:06 +0000 you wrote:
> Kernel side (net-next), which adds NHA_DST_PORT and is the reason for
> this change:
> 
>   net: nexthop: per-nexthop UDP dst port for fdb (VXLAN) nexthops
>   https://lore.kernel.org/netdev/20260723-b4-vxlan-fdb-port-v4-0-46e3a2dd88a3@gmail.com/
> 
> Signed-off-by: Jack Ma <jack4it@gmail.com>
> 
> [...]

Here is the summary with links:
  - [iproute2-next,v2,1/2] uapi: add NHA_DST_PORT
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=68f2b2cc05d3
  - [iproute2-next,v2,2/2] ip nexthop: support fdb destination port
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=ad2b2d95fd11

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-08-03 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  1:25 [PATCH iproute2-next v2 0/2] ip nexthop: support fdb destination port Jack Ma
2026-07-23  1:25 ` [PATCH iproute2-next v2 1/2] uapi: add NHA_DST_PORT Jack Ma
2026-07-23  1:25 ` [PATCH iproute2-next v2 2/2] ip nexthop: support fdb destination port Jack Ma
2026-07-23  7:49   ` Ido Schimmel
2026-08-03 18:10 ` 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=178578061514.2763391.9165782985549600808.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=jack4it@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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.