All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC PATCH 4.4] Documentation/network: reword kernel version reference
@ 2019-02-15 16:19 Mark Rustad
  2019-02-18  1:36 ` Sasha Levin
  0 siblings, 1 reply; 2+ messages in thread
From: Mark Rustad @ 2019-02-15 16:19 UTC (permalink / raw)
  To: gregkh, linux-kernel, stable

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.


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [RFC PATCH 4.4] Documentation/network: reword kernel version reference
  2019-02-15 16:19 [RFC PATCH 4.4] Documentation/network: reword kernel version reference Mark Rustad
@ 2019-02-18  1:36 ` Sasha Levin
  0 siblings, 0 replies; 2+ messages in thread
From: Sasha Levin @ 2019-02-18  1:36 UTC (permalink / raw)
  To: Mark Rustad; +Cc: gregkh, linux-kernel, stable

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-02-18  1:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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.