From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Taniya Das <tdas@codeaurora.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: Re: [PATCH v1 1/4] clk: qcom: sc7280: Update clk_init_data to const for GCC
Date: Thu, 17 Feb 2022 14:44:09 -0800 [thread overview]
Message-ID: <20220217224411.62509C340E8@smtp.kernel.org> (raw)
In-Reply-To: <20220202183528.3911-1-tdas@codeaurora.org>
Quoting Taniya Das (2022-02-02 10:35:25)
> Update clk_init_data to const and also use index instead of fw_name for
> global clock controller.
Yes but why?
>
> Fixes: a3cc092196ef6 ("clk: qcom: Add Global Clock controller (GCC) driver for SC7280")
> Signed-off-by: Taniya Das <tdas@codeaurora.org>
> ---
I guess this supersedes the singleton patch? Can you please send a cover
letter for multi-patch series?
next prev parent reply other threads:[~2022-02-17 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 18:35 [PATCH v1 1/4] clk: qcom: sc7280: Update clk_init_data to const for GCC Taniya Das
2022-02-02 18:35 ` [PATCH v1 2/4] clk: qcom: sc7280: Update clk_init_data to const for CAMCC Taniya Das
2022-02-02 18:35 ` [PATCH v1 3/4] clk: qcom: sc7280: Update clk_init_data to const for DISPCC Taniya Das
2022-02-02 18:35 ` [PATCH v1 4/4] clk: qcom: sc7280: Update clk_init_data to const for clock controllers Taniya Das
2022-02-17 22:44 ` Stephen Boyd [this message]
2022-06-24 17:08 ` [PATCH v1 1/4] clk: qcom: sc7280: Update clk_init_data to const for GCC Bjorn Andersson
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=20220217224411.62509C340E8@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=tdas@codeaurora.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.