From: "Maxime Ripard" <mripard@kernel.org>
To: "Brian Masney" <bmasney@redhat.com>
Cc: linux-clk@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Maxime Ripard" <mripard@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Stephen Boyd" <sboyd@kernel.org>
Subject: Re: [PATCH v3 1/4] clk: add kernel docs for the core flags
Date: Wed, 13 May 2026 05:48:12 +0000 [thread overview]
Message-ID: <b013e768b881741f45fd6137c325b599@kernel.org> (raw)
In-Reply-To: <20260511-clk-docs-v3-1-ed67e1065809@redhat.com>
On Mon, 11 May 2026 21:35:04 -0400, Brian Masney wrote:
> Let's add a DOC section for the clk core flags, and move the
> documentation for each flag into the doc header so that it can
> be easily referenced in the generated kernel documentation.
>
> Note: The comment about "Please update clk_flags..." is included as a
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2026-05-13 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 1:35 [PATCH v3 0/4] clk: update kernel docs Brian Masney
2026-05-12 1:35 ` [PATCH v3 1/4] clk: add kernel docs for the core flags Brian Masney
2026-05-13 5:48 ` Maxime Ripard [this message]
2026-05-12 1:35 ` [PATCH v3 2/4] clk: add kernel docs for struct clk_core Brian Masney
2026-05-12 21:22 ` Randy Dunlap
2026-05-13 5:48 ` Maxime Ripard
2026-05-12 1:35 ` [PATCH v3 3/4] docs: clk: include some identifiers to keep documentation up to date Brian Masney
2026-05-12 21:22 ` Randy Dunlap
2026-05-13 5:48 ` Maxime Ripard
2026-05-12 1:35 ` [PATCH v3 4/4] clk: test: convert constants to use HZ_PER_MHZ Brian Masney
2026-05-13 5:49 ` Maxime Ripard
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=b013e768b881741f45fd6137c325b599@kernel.org \
--to=mripard@kernel.org \
--cc=bmasney@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.