From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: shmobile: r8a7790: don't use external clock for SCIFs
Date: Mon, 17 Jun 2013 11:25:00 +0900 [thread overview]
Message-ID: <20130617022459.GL15043@verge.net.au> (raw)
In-Reply-To: <20130615010456.GP18124@quad.lixom.net>
On Fri, Jun 14, 2013 at 06:04:56PM -0700, Olof Johansson wrote:
> On Thu, Jun 13, 2013 at 04:00:54PM +0900, Simon Horman wrote:
> > From: Ulrich Hecht <ulrich.hecht@gmail.com>
> >
> > This is an external component and may or may not be there, while the
> > internal clock always works.
> >
> > Signed-off-by: Ulrich Hecht <ulrich.hecht@gmail.com>
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> Looks like this one is appropriate for arm-soc merging, but I'll hold off
> pulling this branch until the serial driver piece has been acked or dropped (to
> be merged by Greg).
This patch has a build-time dependency on the serial driver piece,
which is why I included both patches in the same pull-request.
I'll talk with Greg to see how he would like to move this forwards.
next prev parent reply other threads:[~2013-06-17 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 7:00 [GIT PULL 0/2] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-13 7:00 ` [PATCH 1/2] serial: sh-sci: HSCIF support Simon Horman
2013-06-15 1:03 ` Olof Johansson
2013-06-13 7:00 ` [PATCH 2/2] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
2013-06-15 1:04 ` Olof Johansson
2013-06-17 2:25 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-17 2:42 [PATCH 0/2] serial: sh-sci: HSCIF support Simon Horman
2013-06-17 2:42 ` [PATCH 2/2] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
2013-06-17 3:38 [GIT PULL 0/2 v2] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-17 3:38 ` [PATCH 2/2] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
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=20130617022459.GL15043@verge.net.au \
--to=horms@verge.net.au \
--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