From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
linux-omap@vger.kernel.org, linux-input@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] Keyboard: omap-keypad: use matrix_keypad.h
Date: Mon, 20 Dec 2010 10:02:08 -0800 [thread overview]
Message-ID: <20101220180207.GD9353@core.coreip.homeip.net> (raw)
In-Reply-To: <201012201832.24243.jkrzyszt@tis.icnet.pl>
On Mon, Dec 20, 2010 at 06:32:22PM +0100, Janusz Krzysztofik wrote:
> Monday 20 December 2010 16:29:32 Aaro Koskinen wrote:
> > Hello,
> >
> > On Sat, 18 Dec 2010, Janusz Krzysztofik wrote:
> > > Most keypad drivers make use of the <linux/input/matrix_keypad.h>
> > > defined macros, structures and inline functions.
> > >
> > > Convert omap-keypad driver to use those as well, as suggested by a
> > > compile time warning, hardcoded into the OMAP <palt/keypad.h>.
> > >
> > > Created against linux-2.6.37-rc5.
> > > Tested on Amstrad Delta.
> > > Compile tested with omap1_defconfig and omap2plus_defconfig
> > > shrinked to board-h4.
> > >
> > > Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
> >
> > [...]
> >
> > > --- linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c.orig
> > > 2010-12-09 23:07:35.000000000 +0100 +++
> > > linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c
> > > 2010-12-18 16:23:29.000000000 +0100 @@ -46,81 +46,79 @@ static u16
> > > ams_delta_latch2_reg;
> > > static int ams_delta_keymap[] = {
> >
> > [...]
> >
> > > +static const struct matrix_keymap_data ams_delta_keymap_data = {
> > > + .keymap = ams_delta_keymap,
> > > + .keymap_size = ARRAY_SIZE(ams_delta_keymap),
> > > +};
> >
> > You should update the ams_delta_keymap type as well, otherwise this
> > patch will introduce the following sparse warning:
> >
> > CHECK arch/arm/mach-omap1/board-ams-delta.c
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: warning: incorrect type in initializer (different signedness)
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: expected unsigned int const [usertype] *keymap
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: got int static [toplevel] *<noident>
>
> Hi Aaro,
> How did you get this output? I'm using OpenEmbedded as my development
> environment. Running make with "C=1" (EXTRA_OEMAKE=" C=1 ") displays a
> lot but the above. Running sparse by hand breaks with "unable to
> open 'linux/init.h'". Any advice?
>
Not sure why exactly your sparse does not pick it up (too old maybe?)
but the following:
--- linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c.orig 2010-12-09 23:07:35.000000000 +0100
+++ linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c 2010-12-18 16:23:29.000000000 +0100
@@ -46,81 +46,79 @@ static u16 ams_delta_latch2_reg;
static int ams_delta_keymap[] = {
KEY(0, 0, KEY_F1), /* Advert */
should be
static const unisgned int ams_delta_keymap[] = {
Same goes for the rest of keymaps.
Thanks.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Keyboard: omap-keypad: use matrix_keypad.h
Date: Mon, 20 Dec 2010 10:02:08 -0800 [thread overview]
Message-ID: <20101220180207.GD9353@core.coreip.homeip.net> (raw)
In-Reply-To: <201012201832.24243.jkrzyszt@tis.icnet.pl>
On Mon, Dec 20, 2010 at 06:32:22PM +0100, Janusz Krzysztofik wrote:
> Monday 20 December 2010 16:29:32 Aaro Koskinen wrote:
> > Hello,
> >
> > On Sat, 18 Dec 2010, Janusz Krzysztofik wrote:
> > > Most keypad drivers make use of the <linux/input/matrix_keypad.h>
> > > defined macros, structures and inline functions.
> > >
> > > Convert omap-keypad driver to use those as well, as suggested by a
> > > compile time warning, hardcoded into the OMAP <palt/keypad.h>.
> > >
> > > Created against linux-2.6.37-rc5.
> > > Tested on Amstrad Delta.
> > > Compile tested with omap1_defconfig and omap2plus_defconfig
> > > shrinked to board-h4.
> > >
> > > Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
> >
> > [...]
> >
> > > --- linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c.orig
> > > 2010-12-09 23:07:35.000000000 +0100 +++
> > > linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c
> > > 2010-12-18 16:23:29.000000000 +0100 @@ -46,81 +46,79 @@ static u16
> > > ams_delta_latch2_reg;
> > > static int ams_delta_keymap[] = {
> >
> > [...]
> >
> > > +static const struct matrix_keymap_data ams_delta_keymap_data = {
> > > + .keymap = ams_delta_keymap,
> > > + .keymap_size = ARRAY_SIZE(ams_delta_keymap),
> > > +};
> >
> > You should update the ams_delta_keymap type as well, otherwise this
> > patch will introduce the following sparse warning:
> >
> > CHECK arch/arm/mach-omap1/board-ams-delta.c
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: warning: incorrect type in initializer (different signedness)
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: expected unsigned int const [usertype] *keymap
> > arch/arm/mach-omap1/board-ams-delta.c:191:27: got int static [toplevel] *<noident>
>
> Hi Aaro,
> How did you get this output? I'm using OpenEmbedded as my development
> environment. Running make with "C=1" (EXTRA_OEMAKE=" C=1 ") displays a
> lot but the above. Running sparse by hand breaks with "unable to
> open 'linux/init.h'". Any advice?
>
Not sure why exactly your sparse does not pick it up (too old maybe?)
but the following:
--- linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c.orig 2010-12-09 23:07:35.000000000 +0100
+++ linux-2.6.37-rc5/arch/arm/mach-omap1/board-ams-delta.c 2010-12-18 16:23:29.000000000 +0100
@@ -46,81 +46,79 @@ static u16 ams_delta_latch2_reg;
static int ams_delta_keymap[] = {
KEY(0, 0, KEY_F1), /* Advert */
should be
static const unisgned int ams_delta_keymap[] = {
Same goes for the rest of keymaps.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-12-20 18:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 22:32 [PATCH] Keyboard: omap-keypad: use matrix_keypad.h Janusz Krzysztofik
2010-12-17 22:32 ` Janusz Krzysztofik
2010-12-18 3:10 ` Tony Lindgren
2010-12-18 3:10 ` Tony Lindgren
2010-12-18 4:29 ` Cory Maccarrone
2010-12-18 4:29 ` Cory Maccarrone
2010-12-18 5:29 ` Cory Maccarrone
2010-12-18 5:29 ` Cory Maccarrone
2010-12-18 5:38 ` Cory Maccarrone
2010-12-18 5:38 ` Cory Maccarrone
2010-12-18 6:01 ` Dmitry Torokhov
2010-12-18 6:01 ` Dmitry Torokhov
2010-12-18 11:31 ` Janusz Krzysztofik
2010-12-18 11:31 ` Janusz Krzysztofik
2010-12-18 15:39 ` [PATCH v2] " Janusz Krzysztofik
2010-12-18 15:39 ` Janusz Krzysztofik
2010-12-20 15:29 ` Aaro Koskinen
2010-12-20 15:29 ` Aaro Koskinen
2010-12-20 17:32 ` Janusz Krzysztofik
2010-12-20 17:32 ` Janusz Krzysztofik
2010-12-20 18:02 ` Dmitry Torokhov [this message]
2010-12-20 18:02 ` Dmitry Torokhov
2010-12-20 18:49 ` Janusz Krzysztofik
2010-12-20 18:49 ` Janusz Krzysztofik
2010-12-20 19:03 ` aaro.koskinen
2010-12-20 19:03 ` aaro.koskinen at nokia.com
2010-12-20 20:21 ` Janusz Krzysztofik
2010-12-20 20:21 ` Janusz Krzysztofik
2010-12-20 21:09 ` [PATCH v3] " Janusz Krzysztofik
2010-12-20 21:09 ` Janusz Krzysztofik
2010-12-21 11:20 ` Aaro Koskinen
2010-12-21 11:20 ` Aaro Koskinen
2010-12-22 10:16 ` Dmitry Torokhov
2010-12-22 10:16 ` Dmitry Torokhov
2010-12-22 19:25 ` Tony Lindgren
2010-12-22 19:25 ` Tony Lindgren
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=20101220180207.GD9353@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=aaro.koskinen@nokia.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.