public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Yang Xiwen via B4 Relay  <devnull+forbidden405.outlook.com@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yang Xiwen <forbidden405@outlook.com>
Subject: [PATCH v3 0/2] clk: fix corner case of clk_mux_determine_rate_flags()
Date: Thu, 27 Apr 2023 03:34:15 +0800	[thread overview]
Message-ID: <20230421-clk-v3-0-9ff79e7e7fed@outlook.com> (raw)

Signed-off-by: Yang Xiwen <forbidden405@outlook.com>
---
Changes in v3:
- Add many unittest functions for mux determine_rate
- Add more checks for ULONG_MAX
- Link to v2: https://lore.kernel.org/r/20230421-clk-v2-0-74c6cc2214d1@outlook.com

Changes in v2:
- Add a unit test to clk_test.c
- Link to v1: https://lore.kernel.org/r/20230421-clk-v1-1-bb503f2f2cf3@outlook.com

---
Yang Xiwen (2):
      clk: use ULONG_MAX as the initial value for the iteration in clk_mux_determine_rate_flags()
      clk: tests: Add missing test cases for mux determine_rate

 drivers/clk/clk.c      |  13 ++++-
 drivers/clk/clk_test.c | 131 ++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 141 insertions(+), 3 deletions(-)
---
base-commit: 76f598ba7d8e2bfb4855b5298caedd5af0c374a8
change-id: 20230421-clk-64c6b6e21cdb

Best regards,
-- 
Yang Xiwen <forbidden405@outlook.com>


             reply	other threads:[~2023-04-26 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 19:34 Yang Xiwen via B4 Relay [this message]
2023-04-26 19:34 ` [PATCH v3 1/2] clk: use ULONG_MAX as the initial value for the iteration in clk_mux_determine_rate_flags() Yang Xiwen via B4 Relay
2023-04-26 19:34 ` [PATCH v3 2/2] clk: tests: Add missing test cases for mux determine_rate Yang Xiwen via B4 Relay
2023-05-03  3:08   ` Stephen Boyd
2023-05-03 11:53     ` Yang Xiwen
2023-05-03 18:44     ` Yang Xiwen
2023-05-03 22:50       ` Stephen Boyd

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=20230421-clk-v3-0-9ff79e7e7fed@outlook.com \
    --to=devnull+forbidden405.outlook.com@kernel.org \
    --cc=forbidden405@outlook.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.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