From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: "Oscar Alejandro Sánchez Lucero" <aleszlucero@gmail.com>,
"Liam R. Howlett" <liam@infradead.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Michal Hocko" <mhocko@suse.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/folio_batch: document missing struct members
Date: Fri, 13 Nov 2026 14:11:10 +0000 [thread overview]
Message-ID: <avcabz1mf4Zo27DW@gremlin> (raw)
In-Reply-To: <5ca50c99-8dfb-42b1-b593-16bf264581e8@kernel.org>
On Fri, Nov 13, 2026 at 11:17:49AM +0100, David Hildenbrand (Arm) wrote:
> On 11/13/26 05:10, Oscar Alejandro Sánchez Lucero wrote:
> > Add missing kernel-doc descriptions for @nr, @i, @percpu_pvec_drained,
> > and @folios in struct folio_batch to fix warnings.
> >
> > Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
> > ---
> > include/linux/folio_batch.h | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/include/linux/folio_batch.h b/include/linux/folio_batch.h
> > index b45946adc50b..7731dcd249a8 100644
> > --- a/include/linux/folio_batch.h
> > +++ b/include/linux/folio_batch.h
> > @@ -18,6 +18,11 @@ struct folio;
> >
> > /**
> > * struct folio_batch - A collection of folios.
> > + * @nr: Number of folios currently in the batch.
> > + * @i: Index of the next folio to process in folio_batch_next().
> > + * @percpu_pvec_drained: Whether the per-CPU deferred LRU queues have already
> > + * been drained during __folio_batch_release().
> > + * @folios: Array of pointers to the folios in the batch.
> > *
> > * The folio_batch is used to amortise the cost of retrieving and
> > * operating on a set of folios. The order of folios in the batch may be
> >
> > ---
> > base-commit: 9d66f26fefacebfeed15de31c1123451a17ff119
> > change-id: 20261112-folio-batch-doc-fa4f7e18ec85
> >
> > Best regards,
>
> Waiting for more review before queuing this.
Dreams do come true ;)
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
>
> Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
>
> --
> Cheers,
>
> David
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-11-13 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 4:10 Oscar Alejandro Sánchez Lucero
2026-11-13 10:17 ` David Hildenbrand (Arm)
2026-11-13 14:11 ` Lorenzo Stoakes (ARM) [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=avcabz1mf4Zo27DW@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aleszlucero@gmail.com \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®