[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250701174621.5e8812ce@mordecai.tesarici.cz>
Date: Tue, 1 Jul 2025 17:46:21 +0200
From: Petr Tesarik <ptesarik@...e.com>
To: Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>, Robin Murphy
<robin.murphy@....com>, Marek Szyprowski <m.szyprowski@...sung.com>, Andrew
Morton <akpm@...ux-foundation.org>, Keith Busch <kbusch@...nel.org>, Jens
Axboe <axboe@...nel.dk>, Bagas Sanjaya <bagasdotme@...il.com>, "open
list:DOCUMENTATION" <linux-doc@...r.kernel.org>, open list
<linux-kernel@...r.kernel.org>, "open list:MEMORY MANAGEMENT"
<linux-mm@...ck.org>
Subject: Re: [PATCH v2 4/8] docs: dma-api: add a kernel-doc comment for
dma_pool_zalloc()
On Tue, 01 Jul 2025 06:54:47 -0600
Jonathan Corbet <corbet@....net> wrote:
> Petr Tesarik <ptesarik@...e.com> writes:
>
> > Do I have to submit a v3 then?
>
> What path were you planning for this to go upstream? If it goes through
> docs, I can apply that tweak on the way in.
There's a reason I put docs: in the Subject prefix. ;-)
This specific patch touches an include file outside Documentation/, but
since it merely adds a kernel-doc comment, I believe it's still good to
go through docs.
Thanks
Petr T
Powered by blists - more mailing lists