From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Maxwell <jmaxwell37@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
martin.lau@kernel.org, joel@joelfernandes.org,
paulmck@kernel.org, eyal.birger@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrea.mayer@uniroma2.it
Subject: Re: [net-next v2] ipv6: remove max_size check inline with ipv4
Date: Sat, 14 Jan 2023 05:40:17 +0000 [thread overview]
Message-ID: <167367481721.11900.11121412923866916372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230112012532.311021-1-jmaxwell37@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Jan 2023 12:25:32 +1100 you wrote:
> v2: Correct syntax error in net/ipv6/route.c
>
> In ip6_dst_gc() replace:
>
> if (entries > gc_thresh)
>
> With:
>
> [...]
Here is the summary with links:
- [net-next,v2] ipv6: remove max_size check inline with ipv4
https://git.kernel.org/netdev/net-next/c/af6d10345ca7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-14 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 1:25 [net-next v2] ipv6: remove max_size check inline with ipv4 Jon Maxwell
2023-01-12 20:41 ` Andrea Mayer
2023-01-12 21:48 ` Jonathan Maxwell
2023-01-12 22:26 ` Andrea Mayer
2023-01-13 4:03 ` David Ahern
2023-01-14 5:40 ` patchwork-bot+netdevbpf [this message]
2023-01-14 14:05 kernel test robot
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=167367481721.11900.11121412923866916372.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=jmaxwell37@gmail.com \
--cc=joel@joelfernandes.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--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.