From: patchwork-bot+netdevbpf@kernel.org
To: Jonas Gorski <jonas.gorski@bisdn.de>
Cc: enachman@marvell.com, taras.chornyi@plvision.eu,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yevhen.orlov@plvision.eu,
oleksandr.mazur@plvision.eu, tchornyi@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: marvell: prestera: fix handling IPv4 routes with nhid
Date: Tue, 08 Aug 2023 22:00:21 +0000 [thread overview]
Message-ID: <169153202180.6931.3528754559838850676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804101220.247515-1-jonas.gorski@bisdn.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Aug 2023 12:12:20 +0200 you wrote:
> Fix handling IPv4 routes referencing a nexthop via its id by replacing
> calls to fib_info_nh() with fib_info_nhc().
>
> Trying to add an IPv4 route referencing a nextop via nhid:
>
> $ ip link set up swp5
> $ ip a a 10.0.0.1/24 dev swp5
> $ ip nexthop add dev swp5 id 20 via 10.0.0.2
> $ ip route add 10.0.1.0/24 nhid 20
>
> [...]
Here is the summary with links:
- net: marvell: prestera: fix handling IPv4 routes with nhid
https://git.kernel.org/netdev/net/c/2aa71b4b294e
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:[~2023-08-08 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 10:12 [PATCH] net: marvell: prestera: fix handling IPv4 routes with nhid Jonas Gorski
2023-08-06 6:33 ` [EXT] " Elad Nachman
2023-08-08 22: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=169153202180.6931.3528754559838850676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enachman@marvell.com \
--cc=jonas.gorski@bisdn.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleksandr.mazur@plvision.eu \
--cc=pabeni@redhat.com \
--cc=taras.chornyi@plvision.eu \
--cc=tchornyi@marvell.com \
--cc=yevhen.orlov@plvision.eu \
/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