mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Edward Cree <ecree.xilinx@gmail.com>
To: Jon Maxwell <jmaxwell37@gmail.com>, davem@davemloft.net
Cc: 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 v3] ipv6: Document that max_size sysctl is depreciated
Date: Fri, 20 Jan 2023 23:03:55 +0000	[thread overview]
Message-ID: <5429676d-13b3-3f9e-b76d-8f794add0fc4@gmail.com> (raw)
In-Reply-To: <20230119224049.1187142-1-jmaxwell37@gmail.com>

On 19/01/2023 22:40, Jon Maxwell wrote:
> v3: Change kernel version from 6.2 to 6.3. Add "commit" in front of hash.
> 
> Document that max_size is depreciated due to:

typo: deprecated (also in Subject line).

> 
> commit af6d10345ca7 ("ipv6: remove max_size check inline with ipv4")
> 
> 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..4cc2fab58dea 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.3 onwards, this is deprecated for ipv6
> +	as garbage collection manages cached route entries.
> +
>  neigh/default/gc_thresh1 - INTEGER
>  	Minimum number of entries to keep.  Garbage collector will not
>  	purge entries if there are fewer than this number.
> 


      reply	other threads:[~2023-01-20 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 22:40 Jon Maxwell
2023-01-20 23:03 ` Edward Cree [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=5429676d-13b3-3f9e-b76d-8f794add0fc4@gmail.com \
    --to=ecree.xilinx@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome