From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: imx: add cpufreq support for i.mx6sx
Date: Mon, 18 Aug 2014 13:24:17 +0800 [thread overview]
Message-ID: <20140818052415.GA31608@dragon> (raw)
In-Reply-To: <20140626055431.GC7859@dragon>
On Thu, Jun 26, 2014 at 01:54:32PM +0800, Shawn Guo wrote:
> So it's because the driver change for imx6sx hasn't been in place. I
> just dropped the patch from my branch for now, and will revisit later
> when driver part shows up on my branch. (Unfortunately, that will be
> next cycle).
The driver change is in v3.17-rc1, so I applies the dts patch.
Shawn
prev parent reply other threads:[~2014-08-18 5:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 9:10 [PATCH V2] ARM: imx: add cpufreq support for i.mx6sx Anson Huang
2014-06-25 9:33 ` Viresh Kumar
2014-06-25 16:14 ` Shawn Guo
2014-06-26 1:23 ` Fabio Estevam
2014-06-26 1:55 ` Fabio Estevam
2014-06-26 2:53 ` Anson.Huang at freescale.com
2014-06-26 3:06 ` Fabio Estevam
2014-06-26 3:11 ` Fabio Estevam
2014-06-26 3:15 ` Anson.Huang at freescale.com
2014-06-26 3:21 ` Fabio Estevam
2014-06-26 3:21 ` Shawn Guo
2014-06-26 5:54 ` Shawn Guo
2014-06-26 7:34 ` Anson.Huang at freescale.com
2014-08-18 5:24 ` Shawn Guo [this message]
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=20140818052415.GA31608@dragon \
--to=shawn.guo@freescale.com \
--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).