SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/8] ARM: shmobile: board used FSI driver's clock
Date: Thu, 08 Nov 2012 06:17:19 +0000	[thread overview]
Message-ID: <20121108061717.GA13151@verge.net.au> (raw)
In-Reply-To: <87625g23os.wl%kuninori.morimoto.gx@renesas.com>

On Thu, Nov 08, 2012 at 03:10:42PM +0900, Simon Horman wrote:
> On Wed, Nov 07, 2012 at 09:56:33PM -0800, Kuninori Morimoto wrote:
> > 
> > Hi Simon
> > 
> > > > Kuninori Morimoto (8):
> > > >   1) ARM: shmobile: add fsi external clock on r8a7740
> > > >   2) ARM: shmobile: add fsi external clock sh7372
> > > >   3) ARM: shmobile: mackerel: enable DMAEngine on USB Host
> > > >   4) ARM: shmobile: use FSI driver's audio clock on armadillo800eva
> > > >   5) ARM: shmobile: use FSI driver's audio clock on mackerel
> > > >   6) ARM: shmobile: use FSI driver's audio clock on ap4evb
> > > >   7) ARM: shmobile: sh7372: remove fsidivx clock
> > > >   8) ARM: shmobile: sh7372: sh7372_fsiXck_clk become non-global
> > (snip)
> > > Thanks, I plan to apply 1, 2, 7 & 8 to the soc branch of the renesas tree and;
> > > 3 - 6 to the boards branch of the reneas stree.
> > > 
> > > However, I am getting conflicts when applying your patches.
> > > Could you either:
> > > 
> > > 1. Split the series in two
> > > 
> > >    a) 1, 2, 7 & 8 based on the soc branch of the renesas tree and;
> > >    b) 3 - 6 based on the boards branch of the renesas tree
> > > 
> > > 2. Rebase the series on the next branch in the renesas tree.
> > 
> > I see, but I couldn't.
> > Because FSI patch-set depends on FSI-DVI patch
> > 
> > d5a1a6ca8c142a9b0b1120d303ee90e86a7e83c2
> > (ARM: shmobile: sh7372: use sh_clk_fsidiv_register() for FSI-DIV clocks)
> 
> That commit is in the boards branch as far as I can see.
> I will try to apply the board patches, they may be ok.
> It was the first two soc patches that I had trouble with.
> 
> > and I find it on simon/boards branch (not soc branch).
> >                  ~~~~~~~~~~~~
> 
> Strange, it seems to be here
> http://git.kernel.org/?p=linux/kernel/git/horms/renesas.git;a=shortlog;h=refs/heads/soc
> 
> > What should I do in this case ?
> 
> Can you try to check your remote and fetch again?
> 
> If that fails I can manually apply the changes and send them to you for
> review.

Sorry, I've noticed some problems with my branches.
I'll shake them out and get back to you ASAP.

  parent reply	other threads:[~2012-11-08  6:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  3:07 [PATCH 0/8] ARM: shmobile: board used FSI driver's clock Kuninori Morimoto
2012-11-08  5:47 ` Simon Horman
2012-11-08  5:56 ` Kuninori Morimoto
2012-11-08  5:58 ` Paul Mundt
2012-11-08  6:10 ` Simon Horman
2012-11-08  6:17 ` Simon Horman [this message]
2012-11-08  7:29 ` Simon Horman
2012-11-08  7:58 ` Kuninori Morimoto
2012-11-08  9:08 ` 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=20121108061717.GA13151@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.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