From: Jonathan Corbet <corbet@lwn.net>
To: Wren Turkal <wt@penguintechs.org>
Cc: Wren Turkal <wt@penguintechs.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Expose the bus kernel docs to the build docs.
Date: Mon, 15 Mar 2021 13:29:52 -0600 [thread overview]
Message-ID: <87sg4w1ahb.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210308191417.4750-1-wt@penguintechs.org>
Wren Turkal <wt@penguintechs.org> writes:
> Before, the bus type related APIs that were defined in the
> include/linux/device/bus.h were not referenced anywhere in the docs, so
> I linked it to the bus types api documentation.
This should really be phrased in the imperative style as described in
Documentation/process/submitting-patches.rst. I wouldn't ordinarily
reject a patch just for that, but...
> Signed-off-by: Wren Turkal <wt@penguintechs.org>
> ---
> Documentation/driver-api/driver-model/bus.rst | 8 ++++++++
> Documentation/driver-api/infrastructure.rst | 3 +--
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/driver-api/driver-model/bus.rst b/Documentation/driver-api/driver-model/bus.rst
> index 016b15a6e8ea..c53b01e95fd9 100644
> --- a/Documentation/driver-api/driver-model/bus.rst
> +++ b/Documentation/driver-api/driver-model/bus.rst
> @@ -1,3 +1,5 @@
> +.. _bus_types:
> +
> =========
> Bus Types
> =========
> @@ -144,3 +146,9 @@ sysfs directory using::
>
> int bus_create_file(struct bus_type *, struct bus_attribute *);
> void bus_remove_file(struct bus_type *, struct bus_attribute *);
> +
> +Functions and Structures
> +========================
> +
> +.. kernel-doc:: include/linux/device/bus.h
> +.. kernel-doc:: drivers/base/bus.c
> diff --git a/Documentation/driver-api/infrastructure.rst b/Documentation/driver-api/infrastructure.rst
> index 683bd460e222..eb2a2c9e3c0c 100644
> --- a/Documentation/driver-api/infrastructure.rst
> +++ b/Documentation/driver-api/infrastructure.rst
> @@ -41,8 +41,7 @@ Device Drivers Base
> .. kernel-doc:: drivers/base/platform.c
> :export:
>
> -.. kernel-doc:: drivers/base/bus.c
> - :export:
> +:ref:`bus_types`
Rather than inserting labels and making explicit cross-references, it
seems better to just let automarkup do the work for you. So instead of
the above line, something like:
See also Documentation/driver-api/driver-model/bus.rst
Thanks,
jon
prev parent reply other threads:[~2021-03-15 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 1:33 [PATCH] Expose the bus kernel docs to the build docs Wren Turkal
2021-03-07 1:44 ` Matthew Wilcox
2021-03-07 1:46 ` Wren Turkal
2021-03-07 3:12 ` [PATCH v2] " Wren Turkal
2021-03-07 3:16 ` Matthew Wilcox
2021-03-07 3:41 ` Wren Turkal
2021-03-08 19:14 ` [PATCH v3] " Wren Turkal
2021-03-09 20:15 ` Wren Turkal
2021-03-12 18:52 ` Wren Turkal
2021-03-15 19:29 ` 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=87sg4w1ahb.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wt@penguintechs.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