From: Suren Baghdasaryan <surenb@google.com>
To: SeongJae Park <sj@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
akpm@linux-foundation.org, kent.overstreet@linux.dev,
corbet@lwn.net, ranxiaokai627@163.com, ran.xiaokai@zte.com.cn,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] Docs/mm/allocation-profiling: describe sysctrl limitations in debug mode
Date: Fri, 16 Jan 2026 10:45:28 -0800 [thread overview]
Message-ID: <CAJuCfpGS_Kw7O1tTWAVs_6dHMPjewh9NLSB2TNRTKXTcwbq0xw@mail.gmail.com> (raw)
In-Reply-To: <CAJuCfpFevUwXxwOrpH3+VOibjJw0rBw3=QL-nqeKreNEky7_Gg@mail.gmail.com>
On Fri, Jan 16, 2026 at 10:30 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> On Thu, Jan 15, 2026 at 6:18 PM SeongJae Park <sj@kernel.org> wrote:
> >
> > On Thu, 15 Jan 2026 09:05:25 -0800 Suren Baghdasaryan <surenb@google.com> wrote:
> >
> > > On Wed, Jan 14, 2026 at 9:57 PM Matthew Wilcox <willy@infradead.org> wrote:
> > > >
> > > > On Wed, Jan 14, 2026 at 09:45:57PM -0800, Suren Baghdasaryan wrote:
> > > > > + warnings produces by allocations made while profiling is disabled and freed
> > > >
> > > > "produced"
> > >
> > > Thanks! I'll wait for a day and if there are no other objections, I
> > > will post a fixed version.
> >
> > Assuming Matthiew's good finding will be fixed,
> >
> > Acked-by: SeongJae Park <sj@kernel.org>
>
> Thanks!
>
> >
> > Fwiw, the typo is also on the .../sysctl/vm.rst part.
>
> Correct, I'll fix in both places.
v2 is posted at
https://lore.kernel.org/all/20260116184423.2708363-1-surenb@google.com/
>
> > And from the finding, I
> > was wondering if it is better to put the description only one of two documents
> > rather than having the duplication, and further if the 'Usage:' part of
> > allocation-profiling.rst is better to be moved to
> > 'Documentation/admin-guide/mm/'. But I ended up thinking those are too trivial
> > and small things.
>
> Yes, I didn't want to complicate reader's life by adding a reference
> for a couple of sentences.
>
> >
> >
> > Thanks,
> > SJ
prev parent reply other threads:[~2026-01-16 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 5:45 Suren Baghdasaryan
2026-01-15 5:57 ` Matthew Wilcox
2026-01-15 17:05 ` Suren Baghdasaryan
2026-01-16 2:18 ` SeongJae Park
2026-01-16 18:30 ` Suren Baghdasaryan
2026-01-16 18:45 ` Suren Baghdasaryan [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=CAJuCfpGS_Kw7O1tTWAVs_6dHMPjewh9NLSB2TNRTKXTcwbq0xw@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.com \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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