linux-kernel - Re: [PATCH] clk: mxs: Fix the GPMI clock name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120620142643.GD2253@S2101-09.ap.freescale.net>
Date:	Wed, 20 Jun 2012 22:26:45 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Fabio Estevam <festevam@...il.com>
CC:	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <marex@...x.de>,
	<kernel@...gutronix.de>,
	Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH] clk: mxs: Fix the GPMI clock name

On Tue, Jun 19, 2012 at 05:27:32PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@...escale.com>
> 
> The correct name for the GPMI clock is 'gpmi-nand'.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@...escale.com>

Applied, thanks.

Regards,
Shawn

> ---
>  drivers/clk/mxs/clk-imx23.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/clk/mxs/clk-imx23.c b/drivers/clk/mxs/clk-imx23.c
> index f7be225..40ad638 100644
> --- a/drivers/clk/mxs/clk-imx23.c
> +++ b/drivers/clk/mxs/clk-imx23.c
> @@ -106,7 +106,7 @@ static struct clk_lookup lcdif_lookups[] __initdata = {
>  
>  static struct clk_lookup gpmi_lookups[] __initdata = {
>  	{ .dev_id = "imx23-gpmi-nand", },
> -	{ .dev_id = "8000c000.gpmi", },
> +	{ .dev_id = "8000c000.gpmi-nand", },
>  };
>  
>  static const char *sel_pll[]  __initconst = { "pll", "ref_xtal", };
> -- 
> 1.7.1
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/