From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Georgi Djakov <georgi.djakov@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk <linux-clk@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v3] clk: qcom: msm8916: Don't build drivers by default
Date: Fri, 21 Jun 2019 13:36:00 +0200 [thread overview]
Message-ID: <d6f20e7b-2609-faf3-3dfa-aba644d8a9b6@free.fr> (raw)
In-Reply-To: <fe935706-b18d-8966-a447-c1fb2be25c85@linaro.org>
On 19/06/2019 15:47, Georgi Djakov wrote:
> On 19.06.19 14:44, Marc Gonzalez wrote:
>
>> QCOM_A53PLL and QCOM_CLK_APCS_MSM8916 stand out as the only options
>> built by default. List them in defconfig after dropping the default.
>>
>> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> ---
>> arch/arm64/configs/defconfig | 2 ++
>> drivers/clk/qcom/Kconfig | 2 --
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> Sorry, I wasn't very clear. IMHO the defconfig change should be a
> separate patch and the v2 of this patch is ok as it is. It would just
> make things easier to merge.
Oh, I see. Could you give your Ack on patch 2 then?
Would the defconfig change go through the clk tree?
Or maybe through the qcom tree?
Regards.
next prev parent reply other threads:[~2019-06-21 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:44 [PATCH v3] clk: qcom: msm8916: Don't build drivers by default Marc Gonzalez
2019-06-19 13:47 ` Georgi Djakov
2019-06-21 11:36 ` Marc Gonzalez [this message]
2019-06-23 18:54 ` Amit Kucheria
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=d6f20e7b-2609-faf3-3dfa-aba644d8a9b6@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@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;
as well as URLs for NNTP newsgroup(s).