From: Jakub Kicinski <kuba@kernel.org>
To: Jon Maxwell <jmaxwell37@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, 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: Document that max_size sysctl is depreciated
Date: Wed, 18 Jan 2023 20:38:49 -0800 [thread overview]
Message-ID: <20230118203849.7c00187a@kernel.org> (raw)
In-Reply-To: <20230117221858.734596-1-jmaxwell37@gmail.com>
On Wed, 18 Jan 2023 09:18:58 +1100 Jon Maxwell wrote:
> Subject: [net-next v2] ipv6: Document that max_size sysctl is depreciated
>
> v2: use correct commit syntax.
change log under the --- lines
> Document that max_size is depreciated due to:
>
> af6d10345ca7 ("ipv6: remove max_size check inline with ipv4")
^ commit
the word "commit" should be there before the hash
> Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com>
> ---
> Documentation/networking/ip-sysctl.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
> index 7fbd060d6047..edf1fcd10c5c 100644
> --- a/Documentation/networking/ip-sysctl.rst
> +++ b/Documentation/networking/ip-sysctl.rst
> @@ -156,6 +156,9 @@ route/max_size - INTEGER
> From linux kernel 3.6 onwards, this is deprecated for ipv4
> as route cache is no longer used.
>
> + From linux kernel 6.2 onwards, this is deprecated for ipv6
6.2 or 6.3? 6.2 is what's currently in Linus's tree, net-next
is 6.3 and the commit in the commit msg is in net-next only.
> + as garbage collection manages cached route entries.
next prev parent reply other threads:[~2023-01-20 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 22:18 [net-next v2] ipv6: Document that max_size sysctl is depreciated Jon Maxwell
2023-01-19 4:38 ` Jakub Kicinski [this message]
2023-01-19 4:42 ` Jonathan Maxwell
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=20230118203849.7c00187a@kernel.org \
--to=kuba@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=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.