public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jon 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 v4] ipv6: Document that max_size sysctl is deprecated
Date: Tue, 24 Jan 2023 06:10:17 +0000	[thread overview]
Message-ID: <167454061744.14000.1130341385748626372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230120232331.1273881-1-jmaxwell37@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 21 Jan 2023 10:23:31 +1100 you wrote:
> v4: fix deprecated typo.
> 
> Document that max_size is deprecated due to:
> 
> commit af6d10345ca7 ("ipv6: remove max_size check inline with ipv4")
> 
> Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net-next,v4] ipv6: Document that max_size sysctl is deprecated
    https://git.kernel.org/netdev/net-next/c/695a376b59f7

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



      reply	other threads:[~2023-01-24  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 23:23 [net-next v4] ipv6: Document that max_size sysctl is deprecated Jon Maxwell
2023-01-24  6: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=167454061744.14000.1130341385748626372.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox