[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1859d17668d.7b9d5469421579.5464668634216421773@siddh.me>
Date: Wed, 11 Jan 2023 00:40:34 +0530
From: Siddh Raman Pant <code@...dh.me>
To: "David Howells" <dhowells@...hat.com>
Cc: "mauro carvalho chehab" <mchehab@...nel.org>,
"randy dunlap" <rdunlap@...radead.org>,
"jonathan corbet" <corbet@....net>,
"fabio m. de francesco" <fmdefrancesco@...il.com>,
"eric dumazet" <edumazet@...gle.com>,
"christophe jaillet" <christophe.jaillet@...adoo.fr>,
"eric biggers" <ebiggers@...nel.org>,
"keyrings" <keyrings@...r.kernel.org>,
"linux-security-module" <linux-security-module@...r.kernel.org>,
"linux-fsdevel" <linux-fsdevel@...r.kernel.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] include/linux/watch_queue: Improve documentation
On Tue, 10 Jan 2023 19:39:32 +0530, David Howells wrote:
> Please don't.
>
> The structure is documented fully here:
>
> Documentation/core-api/watch_queue.rst
>
> See:
>
> https://docs.kernel.org/core-api/watch_queue.html#event-filtering
>
> The three column approach is much more readable in the code as it doesn't
> separate the descriptions from the things described. Putting things in
> columns has been around for around 6000 years.
>
> David
Okay. Apologies for that.
But what about the second patch? Should I send that without these doc
changes?
Thanks,
Siddh
Powered by blists - more mailing lists