From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Marc Gonzalez <marc.w.gonzalez@free.fr>,
Amit Kucheria <amit.kucheria@linaro.org>,
Andy Gross <agross@kernel.org>,
Georgi Djakov <georgi.djakov@linaro.org>,
linux-clk <linux-clk@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] clk: qcom: msm8916: Add 2 clk options in defconfig
Date: Tue, 27 Aug 2019 09:52:45 -0700 [thread overview]
Message-ID: <20190827165245.GD26807@tuxbook-pro> (raw)
In-Reply-To: <20190827144855.GA17311@centauri>
On Tue 27 Aug 07:48 PDT 2019, Niklas Cassel wrote:
> On Wed, Aug 07, 2019 at 09:29:24PM -0700, Stephen Boyd wrote:
> > Quoting Marc Gonzalez (2019-07-03 07:00:31)
> > > On 24/06/2019 15:57, Amit Kucheria wrote:
> > >
> > > > On Mon, Jun 24, 2019 at 6:56 PM Marc Gonzalez <marc.w.gonzalez@free.fr> wrote:
> > > >>
> > > >> QCOM_A53PLL and QCOM_CLK_APCS_MSM8916 used to be enabled by default
> > > >> in drivers/clk/qcom/Kconfig. A recent patch changed that by dropping
> > > >> the 'default ARCH_QCOM' directive.
> > > >>
> > > >> Add the two options explicitly in the arm64 defconfig, to avoid
> > > >> functional regressions.
> > > >>
> > > >> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
> > > >
> > > > Acked-by: Amit Kucheria <amit.kucheria@linaro.org>
> > >
> > > Stephen,
> > >
> > > Can you take the following two patches through the clk tree?
> > >
> > > [PATCH v2] clk: qcom: msm8916: Don't build by default
> > > [PATCH] clk: qcom: msm8916: Add 2 clk options in defconfig
> > >
> >
> > Did Andy pick up this defconfig change? The subject is misleading.
> > defconfig changes should be something like
>
> Neither Andy nor Bjorn has picked this.
>
> Could you please pick it up? (possibly with subject fixed up)
>
Picked up and updated the subject.
Thanks Marc!
Regards,
Bjorn
> >
> > arm64: defconfig: Add qcom clk options
> >
> > I don't think I need to pick up the defconfig change. It can go through
> > Andy and arm-soc. So I'll just grab the first one and guess it won't
> > break much on the way in.
> >
next prev parent reply other threads:[~2019-08-27 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 15:09 [PATCH v2] clk: qcom: msm8916: Don't build by default Marc Gonzalez
2019-06-13 15:38 ` Bjorn Andersson
2019-06-14 14:08 ` Georgi Djakov
2019-06-24 12:25 ` Georgi Djakov
2019-06-24 13:26 ` [PATCH] clk: qcom: msm8916: Add 2 clk options in defconfig Marc Gonzalez
2019-06-24 13:57 ` Amit Kucheria
2019-07-03 14:00 ` Marc Gonzalez
2019-08-08 4:29 ` Stephen Boyd
2019-08-27 14:48 ` Niklas Cassel
2019-08-27 16:52 ` Bjorn Andersson [this message]
2019-08-08 4:30 ` [PATCH v2] clk: qcom: msm8916: Don't build by default 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=20190827165245.GD26807@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=niklas.cassel@linaro.org \
--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).