From: Jonathan Corbet <corbet@lwn.net>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Hans de Goede <hdegoede@redhat.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Lee Jones <lee.jones@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
Amjad Ouled-Ameur <aouledameur@baylibre.com>,
kernel@pengutronix.de
Subject: Re: [PATCH v2] docs: add a reset controller chapter to the driver API docs
Date: Tue, 8 Dec 2020 10:49:43 -0700 [thread overview]
Message-ID: <20201208104943.499bf52c@lwn.net> (raw)
In-Reply-To: <20201201115754.1713-1-p.zabel@pengutronix.de>
On Tue, 1 Dec 2020 12:57:54 +0100
Philipp Zabel <p.zabel@pengutronix.de> wrote:
> Add initial reset controller API documentation. This is mostly intended
> to describe the concepts to users of the consumer API, and to tie the
> kerneldoc comments we already have into the driver API documentation.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Reviewed-by: Amjad Ouled-Ameur <aouledameur@baylibre.fr>
> ---
> Changes since v1 [1]:
> - Added a note that reset_control_status() does not accept reset control
> array handles (Randy Dunlap)
>
> [1] https://lore.kernel.org/lkml/20201117103306.17010-1-p.zabel@pengutronix.de/
> ---
> Documentation/driver-api/index.rst | 1 +
> Documentation/driver-api/reset.rst | 221 +++++++++++++++++++++++++++++
> MAINTAINERS | 1 +
> 3 files changed, 223 insertions(+)
> create mode 100644 Documentation/driver-api/reset.rst
I've applied this, thanks.
jon
prev parent reply other threads:[~2020-12-08 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:57 [PATCH v2] docs: add a reset controller chapter to the driver API docs Philipp Zabel
2020-12-08 17:49 ` 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=20201208104943.499bf52c@lwn.net \
--to=corbet@lwn.net \
--cc=aouledameur@baylibre.com \
--cc=bgolaszewski@baylibre.com \
--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=p.zabel@pengutronix.de \
--cc=rdunlap@infradead.org \
--cc=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).