linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: fix typo "CONFIG_BRIDGE_DVFS"
Date: Mon, 1 Apr 2013 08:54:15 -0700	[thread overview]
Message-ID: <20130401155414.GE10155@atomide.com> (raw)
In-Reply-To: <1364254205.1390.307.camel@x61.thuisdomein>

* Paul Bolle <pebolle@tiscali.nl> [130325 16:34]:
> Commit 90173882ed15a8034d6d162da5f343a2c7d87587 ("omap: add dsp platform
> device") used CONFIG_BRIDGE_DVFS were it obviously meant
> CONFIG_TIDSPBRIDGE_DVFS. Fix that.
> 
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Untested. As this typo has been in the tree since v2.6.37, this really
> needs some testing.

Thanks, applying into omap-for-v3.10/fixes-non-critical.

Regards,

Tony
 
>  arch/arm/mach-omap2/dsp.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/dsp.c b/arch/arm/mach-omap2/dsp.c
> index b155500..b8208b4 100644
> --- a/arch/arm/mach-omap2/dsp.c
> +++ b/arch/arm/mach-omap2/dsp.c
> @@ -26,7 +26,7 @@
>  #include "control.h"
>  #include "cm2xxx_3xxx.h"
>  #include "prm2xxx_3xxx.h"
> -#ifdef CONFIG_BRIDGE_DVFS
> +#ifdef CONFIG_TIDSPBRIDGE_DVFS
>  #include "omap-pm.h"
>  #endif
>  
> @@ -35,7 +35,7 @@
>  static struct platform_device *omap_dsp_pdev;
>  
>  static struct omap_dsp_platform_data omap_dsp_pdata __initdata = {
> -#ifdef CONFIG_BRIDGE_DVFS
> +#ifdef CONFIG_TIDSPBRIDGE_DVFS
>  	.dsp_set_min_opp = omap_pm_dsp_set_min_opp,
>  	.dsp_get_opp = omap_pm_dsp_get_opp,
>  	.cpu_set_freq = omap_pm_cpu_set_freq,
> -- 
> 1.7.11.7
> 

      reply	other threads:[~2013-04-01 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 23:30 [PATCH] omap: fix typo "CONFIG_BRIDGE_DVFS" Paul Bolle
2013-04-01 15:54 ` Tony Lindgren [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=20130401155414.GE10155@atomide.com \
    --to=tony@atomide.com \
    --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).