All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xiao Liang <shaw.leon@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
	yoshfuji@linux-ipv6.org, kuba@kernel.org, kafai@fb.com
Subject: Re: [PATCH net v3] net: ipv4: Fix rtnexthop len when RTA_FLOW is present
Date: Fri, 24 Sep 2021 13:10:07 +0000	[thread overview]
Message-ID: <163248900768.23178.4654443647284577748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210923150319.974-1-shaw.leon@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Thu, 23 Sep 2021 23:03:19 +0800 you wrote:
> Multipath RTA_FLOW is embedded in nexthop. Dump it in fib_add_nexthop()
> to get the length of rtnexthop correct.
> 
> Fixes: b0f60193632e ("ipv4: Refactor nexthop attributes in fib_dump_info")
> Signed-off-by: Xiao Liang <shaw.leon@gmail.com>
> ---
>  include/net/ip_fib.h     |  2 +-
>  include/net/nexthop.h    |  2 +-
>  net/ipv4/fib_semantics.c | 16 +++++++++-------
>  net/ipv6/route.c         |  5 +++--
>  4 files changed, 14 insertions(+), 11 deletions(-)

Here is the summary with links:
  - [net,v3] net: ipv4: Fix rtnexthop len when RTA_FLOW is present
    https://git.kernel.org/netdev/net/c/597aa16c7824

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



      parent reply	other threads:[~2021-09-24 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 15:03 [PATCH net v3] net: ipv4: Fix rtnexthop len when RTA_FLOW is present Xiao Liang
2021-09-23 15:10 ` David Ahern
2021-09-24 13: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=163248900768.23178.4654443647284577748.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=kafai@fb.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shaw.leon@gmail.com \
    --cc=yoshfuji@linux-ipv6.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.