From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clk: Hi6220: enable stub clock driver for ARCH_HISI
Date: Mon, 14 Nov 2016 18:40:42 -0800 [thread overview]
Message-ID: <20161115024042.GV5177@codeaurora.org> (raw)
In-Reply-To: <20161112120231.GB23848@leoy-linaro>
On 11/12, Leo Yan wrote:
> Hi Stephen,
>
> On Wed, Aug 31, 2016 at 03:40:49PM -0700, Stephen Boyd wrote:
> > On 08/31, Leo Yan wrote:
> > > In current kernel config 'CONFIG_STUB_CLK_HI6220' is disabled by
> > > default, as result stub clock driver has not been registered and
> > > CPUFreq driver cannot work.
> > >
> > > This patch is to enable stub clock driver in config for ARCH_HISI.
> > >
> > > Reported-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> > > Signed-off-by: Leo Yan <leo.yan@linaro.org>
> > > ---
> >
> > Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> We found this patch is missed mainline kernel. So could you help pick
> it? Or do you need me resend this patch?
>
Sure I can fish it out and apply it.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-15 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:50 [PATCH 0/3] arm64: Hikey: enable CPUFreq and thermal drivers Leo Yan
2016-08-31 8:50 ` [PATCH 1/3] clk: Hi6220: enable stub clock driver for ARCH_HISI Leo Yan
2016-08-31 22:40 ` Stephen Boyd
2016-11-12 12:02 ` Leo Yan
2016-11-15 2:40 ` Stephen Boyd [this message]
2016-11-15 2:41 ` Stephen Boyd
2016-11-15 2:43 ` Leo Yan
2016-08-31 8:50 ` [PATCH 2/3] thermal: hisilicon: fix for dependency Leo Yan
2016-11-12 12:05 ` Leo Yan
2016-11-15 12:24 ` Zhang Rui
2016-11-16 5:32 ` Leo Yan
2016-08-31 8:50 ` [PATCH 3/3] arm64: defconfig: enable two common modules for power management Leo Yan
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=20161115024042.GV5177@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).