From: Philipp Zabel <p.zabel@pengutronix.de>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Hans de Goede <hdegoede@redhat.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Lee Jones <lee.jones@linaro.org>,
kernel@pengutronix.de
Subject: Re: [RFC] docs: add a reset controller chapter to the driver API docs
Date: Thu, 24 Oct 2019 10:43:36 +0200 [thread overview]
Message-ID: <cba736f135f150d685ab4efee625d69aa800d1c8.camel@pengutronix.de> (raw)
In-Reply-To: <8e964179-4515-33ea-bdc4-f27daa311267@infradead.org>
Hi Randy,
thank you for the corrections!
On Tue, 2019-10-22 at 20:56 -0700, Randy Dunlap wrote:
> On 10/22/19 9:45 AM, Philipp Zabel wrote:
> > Add initial reset controller API documentation. This is mostly indented
>
> intended
:) Makes me smile every time.
[...]
> > +====================
> > +Reset controller API
> > +====================
> > +
> > +Introduction
> > +============
> > +
> > +Reset controllers are central units that control the reset signals to multiple
> > +peripherals.
> > +The reset controller API is split in two parts:
>
> I prefer into two parts:
Ok. I think this might have come from "split in half".
[...]
> > +Consumer driver interface
> > +=========================
> > +
> > +This interface offers a similar API to the kernel clock framework.
>
> or:
> This interface provides an API that is similar to the kernel clock framework.
Yes, this is better as well. I'll change all three in the next version.
[...]
> > +.. kernel-doc:: drivers/reset/core.c
> > + :functions: of_reset_simple_xlate
> > + reset_controller_register
> > + reset_controller_unregister
> > + devm_reset_controller_register
> > + reset_controller_add_lookup
>
> These header and source files cause a number of kernel-doc warnings
> for which I am sending a patch.
Thank you, I have already sent fixes for the build warnings.
In hindsight, they probably should have been included as a series.
regards
Philipp
prev parent reply other threads:[~2019-10-24 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 16:45 Philipp Zabel
2019-10-22 17:00 ` Jonathan Corbet
2019-10-24 8:18 ` Philipp Zabel
2019-10-23 3:56 ` Randy Dunlap
2019-10-24 8:43 ` Philipp Zabel [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=cba736f135f150d685ab4efee625d69aa800d1c8.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Ramiro.Oliveira@synopsys.com \
--cc=bgolaszewski@baylibre.com \
--cc=corbet@lwn.net \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=hdegoede@redhat.com \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=rdunlap@infradead.org \
--cc=treding@nvidia.com \
--cc=vivek.gautam@codeaurora.org \
--cc=yamada.masahiro@socionext.com \
/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®