From: Sasha Levin <sashal@kernel.org>
To: Mark Rustad <mrustad@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [RFC PATCH 4.4] Documentation/network: reword kernel version reference
Date: Sun, 17 Feb 2019 20:36:32 -0500 [thread overview]
Message-ID: <20190218013632.GQ10616@sasha-vm> (raw)
In-Reply-To: <20190215161955.12119.77812.stgit@mdr-mbp.hsd1.ca.comcast.net>
On Fri, Feb 15, 2019 at 08:19:55AM -0800, Mark Rustad wrote:
>It seemed odd to say "since 4.17" in a 4.4 kernel. Consider
>rewording the reference to indicate where in the stable series
>it was introduced as well as where it originated.
>
>Signed-off-by: Mark Rustad <mrustad@gmail.com>
>
>---
>
>Does this brief elaboration add useful information? It seems to
>me that someone using a particular series of stable kernels would
>find this information to be helpful or at least potentially less
>confusing to a non-developer.
>---
> Documentation/networking/ip-sysctl.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
>index 7c229f59016f..2fb35658d151 100644
>--- a/Documentation/networking/ip-sysctl.txt
>+++ b/Documentation/networking/ip-sysctl.txt
>@@ -116,7 +116,7 @@ ipfrag_high_thresh - LONG INTEGER
> Maximum memory used to reassemble IP fragments.
>
> ipfrag_low_thresh - LONG INTEGER
>- (Obsolete since linux-4.17)
>+ (Obsolete since linux-4.4.174, backported from linux-4.17)
> Maximum memory used to reassemble IP fragments before the kernel
> begins to remove incomplete fragment queues to free up resources.
> The kernel still accepts new fragments for defragmentation.
Admittingly the stabke kernel rules do not allow documentation fixes,
but I can see how this can be confusing, and the fact that someone
actually hit it, wrote a patch and submitted it makes me want to ignore
that rule.
Queued, thank you!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-02-18 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 16:19 [RFC PATCH 4.4] Documentation/network: reword kernel version reference Mark Rustad
2019-02-18 1:36 ` Sasha Levin [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=20190218013632.GQ10616@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrustad@gmail.com \
--cc=stable@vger.kernel.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