linux-kernel - Re: [PATCH] Remove __devinitdata from tc6393xb_mmc

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: <20101019094818.GH2736@sortiz-mobl>
Date:	Tue, 19 Oct 2010 11:48:19 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Marek Vasut <marek.vasut@...il.com>
Cc:	linux-kernel@...r.kernel.org, axel.lin@...il.com,
	hartleys@...ionengravers.com, ian@...menth.co.uk
Subject: Re: [PATCH] Remove __devinitdata from tc6393xb_mmc_resources

Hi Marek,

On Sun, Oct 10, 2010 at 03:55:43AM +0200, Marek Vasut wrote:
> This static struct resource tc6393xb_mmc_resources[] is used in resume function,
> therefore the data can not be wiped after init.
> 
> Also, this causes a section mismatch.
Patch applied, thanks.

Cheers,
Samuel.


> Signed-off-by: Marek Vasut <marek.vasut@...il.com>
> ---
>  drivers/mfd/tc6393xb.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/mfd/tc6393xb.c b/drivers/mfd/tc6393xb.c
> index ef6c42c..1ea80d8 100644
> --- a/drivers/mfd/tc6393xb.c
> +++ b/drivers/mfd/tc6393xb.c
> @@ -155,7 +155,7 @@ static struct resource __devinitdata tc6393xb_nand_resources[] = {
>  	},
>  };
>  
> -static struct resource __devinitdata tc6393xb_mmc_resources[] = {
> +static struct resource tc6393xb_mmc_resources[] = {
>  	{
>  		.start	= 0x800,
>  		.end	= 0x9ff,
> -- 
> 1.7.1
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/