All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: CGEL <cgel.zte@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, corbet@lwn.net,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, xu.xin16@zte.com.cn,
	zealci@zte.com.cn
Subject: Re: [PATCH v2] Documentation: fix outdated interpretation of ip_no_pmtu_disc
Date: Thu, 30 Dec 2021 13:30:09 +0000	[thread overview]
Message-ID: <164087100950.9335.18212536955460808575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211230032856.584972-1-xu.xin16@zte.com.cn>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 30 Dec 2021 03:28:56 +0000 you wrote:
> From: xu xin <xu.xin16@zte.com.cn>
> 
> The updating way of pmtu has changed, but documentation is still in the
> old way. So this patch updates the interpretation of ip_no_pmtu_disc and
> min_pmtu.
> 
> See commit 28d35bcdd3925 ("net: ipv4: don't let PMTU updates increase
> route MTU")
> 
> [...]

Here is the summary with links:
  - [v2] Documentation: fix outdated interpretation of ip_no_pmtu_disc
    https://git.kernel.org/netdev/net/c/be1c5b53227b

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



      reply	other threads:[~2021-12-30 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  3:12 [PATCH linux-next] Documentation: fix outdated interpretation of ip_no_pmtu_disc cgel.zte
2021-12-29 20:15 ` Jakub Kicinski
2021-12-30  3:28   ` [PATCH v2] " cgel.zte
2021-12-30 13:30     ` 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=164087100950.9335.18212536955460808575.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cgel.zte@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xu.xin16@zte.com.cn \
    --cc=zealci@zte.com.cn \
    /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.