From: david@lechnology.com (David Lechner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] da8xx clocks (was part of "da8xx USB clocks")
Date: Thu, 14 Apr 2016 14:26:19 -0500 [thread overview]
Message-ID: <570FEEDB.7000109@lechnology.com> (raw)
In-Reply-To: <1460661217-7389-1-git-send-email-david@lechnology.com>
On 04/14/2016 02:13 PM, David Lechner wrote:
> I have separated these patches from the "da8xx USB clocks" series since that
> series no longer depends on the clock init being moved.
>
> Tested working on the linux-davinci/master branch with LEGO MINDSTORMS EV3.
>
> David Lechner (2):
> ARM: davinci: Move clock init after ioremap.
> ARM: davinci: da850: use clk->set_parent for async3
>
> arch/arm/mach-davinci/clock.c | 2 +-
> arch/arm/mach-davinci/common.c | 6 ---
> arch/arm/mach-davinci/da830.c | 2 +
> arch/arm/mach-davinci/da850.c | 90 ++++++++++++++++++++----------------------
> arch/arm/mach-davinci/dm355.c | 1 +
> arch/arm/mach-davinci/dm365.c | 1 +
> arch/arm/mach-davinci/dm644x.c | 1 +
> arch/arm/mach-davinci/dm646x.c | 1 +
> 8 files changed, 49 insertions(+), 55 deletions(-)
>
Hmm... I was just reviewing my previous emails and you said that you
have already applied these two patches, but they don't seem to have made
it into the linux-davinci/master branch with the others.
next prev parent reply other threads:[~2016-04-14 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 19:13 [PATCH 0/2] da8xx clocks (was part of "da8xx USB clocks") David Lechner
2016-04-14 19:13 ` [PATCH 1/2] ARM: davinci: Move clock init after ioremap David Lechner
2016-04-14 19:13 ` [PATCH 2/2] ARM: davinci: da850: use clk->set_parent for async3 David Lechner
2016-04-16 19:31 ` David Lechner
2016-04-18 4:55 ` Sekhar Nori
2016-04-14 19:26 ` David Lechner [this message]
2016-04-15 6:36 ` [PATCH 0/2] da8xx clocks (was part of "da8xx USB clocks") Sekhar Nori
2016-04-15 10:09 ` Sekhar Nori
2016-04-15 16:21 ` David Lechner
2016-04-27 13:39 ` Sekhar Nori
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=570FEEDB.7000109@lechnology.com \
--to=david@lechnology.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).