All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: sh73a0: Remove duplicate CPUFreq bits
Date: Fri, 22 Aug 2014 03:55:03 +0000	[thread overview]
Message-ID: <20140822035459.GQ9099@verge.net.au> (raw)
In-Reply-To: <20140820130707.350.39869.sendpatchset@w520>

On Wed, Aug 20, 2014 at 10:07:07PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
> 
> The CPUFreq platform device is already registered by
> shmobile_init_late(), so get rid of sh73a0 specific bits.
> 
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>

Thanks, I have queued this up.

> ---
> 
>  Built of top of renesas-devel-20140820-v3.17-rc1
> 
>  arch/arm/mach-shmobile/setup-sh73a0.c |    5 -----
>  1 file changed, 5 deletions(-)
> 
> --- 0001/arch/arm/mach-shmobile/setup-sh73a0.c
> +++ work/arch/arm/mach-shmobile/setup-sh73a0.c	2014-08-19 23:06:54.000000000 +0900
> @@ -775,17 +775,12 @@ void __init sh73a0_add_early_devices(voi
>  
>  void __init sh73a0_add_standard_devices_dt(void)
>  {
> -	struct platform_device_info devinfo = { .name = "cpufreq-cpu0", .id = -1, };
> -
>  	/* clocks are setup late during boot in the case of DT */
>  	sh73a0_clock_init();
>  
>  	platform_add_devices(sh73a0_devices_dt,
>  			     ARRAY_SIZE(sh73a0_devices_dt));
>  	of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> -
> -	/* Instantiate cpufreq-cpu0 */
> -	platform_device_register_full(&devinfo);
>  }
>  
>  static const char *sh73a0_boards_compat_dt[] __initdata = {
> 

      reply	other threads:[~2014-08-22  3:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 13:07 [PATCH] ARM: shmobile: sh73a0: Remove duplicate CPUFreq bits Magnus Damm
2014-08-22  3:55 ` Simon Horman [this message]

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=20140822035459.GQ9099@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.