From: Brian Masney <bmasney@redhat.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Maxime Ripard <mripard@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Masney <bmasney@redhat.com>
Subject: [PATCH 0/2] clk: add kernel docs for struct clk_core and update tests to use HZ_PER_MHZ
Date: Wed, 04 Mar 2026 17:51:02 -0500 [thread overview]
Message-ID: <20260304-clk-docs-v1-0-fee468db99f1@redhat.com> (raw)
Here's two patches from my v4 clk rate change series at [1] that should
hopefully be good to go. This series documents all of the members of
struct clk_core, and updates the kunit tests to use HZ_PER_MHZ.
Changes from what was previously posted:
- Add entry for new field hashtable_node that was recently added.
- Update description of duty member.
[1] https://lore.kernel.org/linux-clk/20250923-clk-tests-docs-v4-0-9205cb3d3cba@redhat.com/
Signed-off-by: Brian Masney <bmasney@redhat.com>
---
Brian Masney (2):
clk: add kernel docs for struct clk_core
clk: test: convert constants to use HZ_PER_MHZ
drivers/clk/clk.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/clk/clk_test.c | 7 +++---
2 files changed, 63 insertions(+), 3 deletions(-)
---
base-commit: fc7b1a72c6cd5cbbd989c6c32a6486e3e4e3594d
change-id: 20260304-clk-docs-0b578f421600
Best regards,
--
Brian Masney <bmasney@redhat.com>
next reply other threads:[~2026-03-04 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 22:51 Brian Masney [this message]
2026-03-04 22:51 ` [PATCH 1/2] clk: add kernel docs for struct clk_core Brian Masney
2026-03-25 2:31 ` Stephen Boyd
2026-03-25 17:36 ` Brian Masney
2026-03-04 22:51 ` [PATCH 2/2] clk: test: convert constants to use HZ_PER_MHZ Brian Masney
2026-03-05 12:12 ` [PATCH 0/2] clk: add kernel docs for struct clk_core and update tests " 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=20260304-clk-docs-v1-0-fee468db99f1@redhat.com \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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
Powered by JetHome