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/5] ARM: shmobile: Add R-Car M1A Bock-W support
Date: Sat, 16 Mar 2013 09:36:11 +0000	[thread overview]
Message-ID: <20130316093610.GC12932@verge.net.au> (raw)
In-Reply-To: <87y5e3pra9.wl%kuninori.morimoto.gx@renesas.com>

On Sat, Mar 16, 2013 at 02:26:56AM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 03/04/2013 10:17 AM, Kuninori Morimoto wrote:
> 
> >These are R-Car M1A chip and Bock-W board support
> >
> >Bock-W board needs ${LINUX}/arch/arm/tools/mach-types
> >
> >bockw                  MACH_BOCKW              BOCKW                   3386
> >
> >ARM Web site already has Bock-W, mach-types will be updated
> >if upstream kernel has it.
> >
> >This series doesn't support DT yet.
> >I'm working for it, but still doesn't work.
> >I will send my current DT support work for R-Car M1,
> >it is very helpful for me if you give feedback.
> >
> >These patches are based on simon/next branch
> >
> >Kuninori Morimoto (5):
> >       ARM: shmobile: add R8A7778 setup support
> >       ARM: shmobile: add R8A7778 clock support
> >       ARM: shmobile: add R8A7778 intc support
> >       ARM: shmobile: add r8a7778 GPIO/PFC support
> 
>    I can't find patch 4 of this series anywhere, and it seems I
> can't build board-bockw.c without it. Was it ever posted?

For the record, I can't locate it either.

  parent reply	other threads:[~2013-03-16  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  7:17 [PATCH 0/5] ARM: shmobile: Add R-Car M1A Bock-W support Kuninori Morimoto
2013-03-15 22:25 ` Sergei Shtylyov
2013-03-16  3:40 ` Magnus Damm
2013-03-16  8:54 ` Simon Horman
2013-03-16  9:36 ` Simon Horman [this message]
2013-03-18  1:34 ` Kuninori Morimoto
2013-03-18  1:56 ` Kuninori Morimoto

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=20130316093610.GC12932@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