linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/10] ARM: shmobile: Use r8a7791_add_standard_devices() on Koelsch
Date: Thu, 03 Oct 2013 04:20:29 +0000	[thread overview]
Message-ID: <20131003042028.GK7925@verge.net.au> (raw)
In-Reply-To: <20131001081202.4136.63858.sendpatchset@w520>

On Tue, Oct 01, 2013 at 05:12:02PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
> 
> Use r8a7791_add_standard_devices() on Koelsch to let
> the C version of the board code add on-chip devices.
> 
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
> 
>  arch/arm/mach-shmobile/board-koelsch.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- 0001/arch/arm/mach-shmobile/board-koelsch.c
> +++ work/arch/arm/mach-shmobile/board-koelsch.c	2013-10-01 16:25:46.000000000 +0900
> @@ -29,7 +29,7 @@
>  static void __init koelsch_add_standard_devices(void)
>  {
>  	r8a7791_clock_init();
> -	r8a7791_add_dt_devices();
> +	r8a7791_add_standard_devices();
>  }
>  
>  static const char * const koelsch_boards_compat_dt[] __initconst = {
> 

Thanks, I have queued this up in the boards3 branch.
It should make it into v3.13 but if not I'll rename the branch
soc after rebasing it on v3.13-rcX which will then be targeted at v3.14.

The boards3 branch includes boards code previously queued up for v3.13
and a merge with soc changes previously queued up for v3.13. The reason
for the merge is to provide various build and run-time dependencies
including the r8a7791 SoC code which this board code uses.

  reply	other threads:[~2013-10-03  4:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  8:11 [PATCH 00/10] ARM: shmobile: r8a7791 SoC and Koelsch update V2 Magnus Damm
2013-10-01  8:11 ` [PATCH 01/10] ARM: shmobile: Introduce r8a7791_add_standard_devices() Magnus Damm
2013-10-03  2:36   ` Simon Horman
2013-10-01  8:12 ` [PATCH 02/10] ARM: shmobile: Use r8a7791_add_standard_devices() on Koelsch Magnus Damm
2013-10-03  4:20   ` Simon Horman [this message]
2013-10-01  8:12 ` [PATCH 03/10] ARM: shmobile: r8a7791 IRQC platform device support Magnus Damm
2013-10-03  2:37   ` Simon Horman
2013-10-01  8:12 ` [PATCH 04/10] ARM: shmobile: r8a7791 IRQC device tree node Magnus Damm
2013-10-03  2:43   ` Simon Horman
2013-10-01  8:12 ` [PATCH 05/10] ARM: shmobile: r8a7791 Arch timer " Magnus Damm
2013-10-03  2:44   ` Simon Horman
2013-10-01  8:12 ` [PATCH 06/10] ARM: shmobile: r8a7791 Arch timer workaround Magnus Damm
2013-10-03  3:45   ` Simon Horman
2013-10-01  8:12 ` [PATCH 07/10] ARM: shmobile: Use arch timer on Koelsch Magnus Damm
2013-10-03  4:21   ` Simon Horman
2013-10-01  8:13 ` [PATCH 08/10] ARM: shmobile: r8a7791 SMP device tree node Magnus Damm
2013-10-03  3:46   ` Simon Horman
2013-10-01  8:13 ` [PATCH 09/10] ARM: shmobile: r8a7791 SMP support Magnus Damm
2013-10-03  3:47   ` Simon Horman
2013-10-01  8:13 ` [PATCH 10/10] ARM: shmobile: Use SMP on Koelsch Magnus Damm
2013-10-03  4:22   ` 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=20131003042028.GK7925@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;
as well as URLs for NNTP newsgroup(s).