From: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: corbet@lwn.net, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, kuba@kernel.org, pabeni@redhat.com,
linux-doc@vger.kernel.org, linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
skhan@linuxfoundation.com, jacob.e.keller@intel.com,
alok.a.tiwari@oracle.com
Subject: Re: [PATCH net-next v4] docs: net: sysctl documentation cleanup
Date: Sun, 22 Jun 2025 12:08:54 +0300 [thread overview]
Message-ID: <CAGn2d8MjZ5J1eMCLaYNdJSbL4nbn9npxLedkRCgBXbfwq2i+Lg@mail.gmail.com> (raw)
In-Reply-To: <aFe62dzYPLktxZrH@archie.me>
On Sun, Jun 22, 2025 at 11:12 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On Sun, Jun 22, 2025 at 09:27:24AM +0300, Abdelrahman Fekry wrote:
> > @@ -1028,13 +1134,15 @@ tcp_shrink_window - BOOLEAN
> > window can be offered, and that TCP implementations MUST ensure
> > that they handle a shrinking window, as specified in RFC 1122.
> >
> > - - 0 - Disabled. The window is never shrunk.
> > - - 1 - Enabled. The window is shrunk when necessary to remain within
> > + Possible values:
> > +
> > + - 0 (disabled) The window is never shrunk.
> > + - 1 (enabled) The window is shrunk when necessary to remain within
> > the memory limit set by autotuning (sk_rcvbuf).
> > This only occurs if a non-zero receive window
> > scaling factor is also in effect.
>
> The indentation for enabled option outputted like a definition list,
> so I fix it up:
>
Noted , fixed it and checked for other problems like this , thank you
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2025-06-22 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 6:27 Abdelrahman Fekry
2025-06-22 8:12 ` Bagas Sanjaya
2025-06-22 9:08 ` Abdelrahman Fekry [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=CAGn2d8MjZ5J1eMCLaYNdJSbL4nbn9npxLedkRCgBXbfwq2i+Lg@mail.gmail.com \
--to=abdelrahmanfekry375@gmail.com \
--cc=alok.a.tiwari@oracle.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.com \
/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
all inboxes | Powered by JetHome®