From: Jonathan Corbet <corbet@lwn.net>
To: Vratislav Bendel <vbendel@redhat.com>, Mike Rapoport <rppt@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jozef Bacik <jobacik@redhat.com>
Subject: Re: [PATCH] docs: mm: fix vm overcommit documentation for OVERCOMMIT_GUESS
Date: Tue, 10 Oct 2023 13:09:58 -0600 [thread overview]
Message-ID: <875y3e70qh.fsf@meer.lwn.net> (raw)
In-Reply-To: <CAHrQN1yOTTMz=RR0rJxr9aFVmTPgYyrabPzNH00Z-fToorrPjQ@mail.gmail.com>
Vratislav Bendel <vbendel@redhat.com> writes:
> On Mon, Aug 29, 2022 at 3:45 PM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Mon, Aug 29, 2022 at 02:46:38PM +0200, vbendel@redhat.com wrote:
> > From: Vratislav Bendel <vbendel@redhat.com>
> >
> > Commit 8c7829b04c52 "mm: fix false-positive OVERCOMMIT_GUESS failures"
> > changed the behavior of the default OVERCOMMIT_GUESS setting.
> > Reflect the change also in the Documentation, namely files:
> > Documentation/admin-guide/sysctl/vm.rst
> > Documentation/mm/overcommit-accounting.rst
> >
> > Reported-by: Jozef Bacik <jobacik@redhat.com>
> > Signed-off-by: Vratislav Bendel <vbendel@redhat.com>
>
> Acked-by: Mike Rapoport <rppt@linux.ibm.com>
>
> Hello,
>
> Poking this one as it's been Acked here without merging for over a
> year. My humble opinion is that Docs should be up to date, reflecting
> the real behavior.
My humble opinion is that I must have screwed up somewhere; not sure how
this fell through the cracks. I've applied it now, thanks and sorry for
the delay.
jon
prev parent reply other threads:[~2023-10-10 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 12:46 [PATCH] docs: mm: fix vm overcommit documentation for OVERCOMMIT_GUESS vbendel
2022-08-29 13:44 ` Mike Rapoport
[not found] ` <CAHrQN1yOTTMz=RR0rJxr9aFVmTPgYyrabPzNH00Z-fToorrPjQ@mail.gmail.com>
2023-10-10 19:09 ` Jonathan Corbet [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=875y3e70qh.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=jobacik@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=vbendel@redhat.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 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.