[PATCH] OMAP: Keypad: Make keypad_data initdata

[PATCH] OMAP: Keypad: Make keypad_data initdata

[Shubhrajyoti D]

The keypad data is accessed only at init so making it initdata.
This removes the section mismatch warning.

Reported-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
---
 arch/arm/mach-omap2/board-4430sdp.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c
index 47e6ab9..2b28c7e 100644
--- a/arch/arm/mach-omap2/board-4430sdp.c
+++ b/arch/arm/mach-omap2/board-4430sdp.c
@@ -195,7 +195,7 @@ static struct omap4_keypad_platform_data sdp4430_keypad_data = {
 	.cols			= 8,
 };
 
-static struct omap_board_data keypad_data = {
+static struct omap_board_data keypad_data __initdata = {
 	.id	    = 1,
 	.pads	 = keypad_pads,
 	.pads_cnt       = ARRAY_SIZE(keypad_pads),
-- 
1.7.1

RE: [PATCH] OMAP: Keypad: Make keypad_data initdata

[Vishwanath Sripathy]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Shubhrajyoti D
> Sent: Tuesday, July 12, 2011 12:02 PM
> To: linux-omap@vger.kernel.org
> Cc: Shubhrajyoti D
> Subject: [PATCH] OMAP: Keypad: Make keypad_data initdata
>
> The keypad data is accessed only at init so making it initdata.
> This removes the section mismatch warning.
>
> Reported-by: Kevin Hilman <khilman@ti.com>
> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
> ---
>  arch/arm/mach-omap2/board-4430sdp.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-
> omap2/board-4430sdp.c
Is this issue only for OMAP4 SDP? What about Panda, Beagle, OMAP3 SDP
boards?
If it's only for OMAP4, pls correct the subject.

Vishwa
> index 47e6ab9..2b28c7e 100644
> --- a/arch/arm/mach-omap2/board-4430sdp.c
> +++ b/arch/arm/mach-omap2/board-4430sdp.c
> @@ -195,7 +195,7 @@ static struct omap4_keypad_platform_data
> sdp4430_keypad_data = {
>  	.cols			= 8,
>  };
>
> -static struct omap_board_data keypad_data = {
> +static struct omap_board_data keypad_data __initdata = {
>  	.id	    = 1,
>  	.pads	 = keypad_pads,
>  	.pads_cnt       = ARRAY_SIZE(keypad_pads),
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] OMAP: Keypad: Make keypad_data initdata

[Shubhrajyoti]

On Tuesday 12 July 2011 12:09 PM, Vishwanath Sripathy wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of Shubhrajyoti D
>> Sent: Tuesday, July 12, 2011 12:02 PM
>> To: linux-omap@vger.kernel.org
>> Cc: Shubhrajyoti D
>> Subject: [PATCH] OMAP: Keypad: Make keypad_data initdata
>>
>> The keypad data is accessed only at init so making it initdata.
>> This removes the section mismatch warning.
>>
>> Reported-by: Kevin Hilman<khilman@ti.com>
>> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
>> ---
>>   arch/arm/mach-omap2/board-4430sdp.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-
>> omap2/board-4430sdp.c
> Is this issue only for OMAP4 SDP? What about Panda, Beagle, OMAP3 SDP
> boards?
> If it's only for OMAP4, pls correct the subject.
Yes will correct the subject line.
> Vishwa
>> index 47e6ab9..2b28c7e 100644
>> --- a/arch/arm/mach-omap2/board-4430sdp.c
>> +++ b/arch/arm/mach-omap2/board-4430sdp.c
>> @@ -195,7 +195,7 @@ static struct omap4_keypad_platform_data
>> sdp4430_keypad_data = {
>>   	.cols			= 8,
>>   };
>>
>> -static struct omap_board_data keypad_data = {
>> +static struct omap_board_data keypad_data __initdata = {
>>   	.id	    = 1,
>>   	.pads	 = keypad_pads,
>>   	.pads_cnt       = ARRAY_SIZE(keypad_pads),
>> --
>> 1.7.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-
>> omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html