From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Arce, Abraham" <x0066660@ti.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>
Subject: Re: [RFC] [PATCH v3 3/4] OMAP4: Keyboard board support
Date: Tue, 1 Jun 2010 07:48:13 +0300 [thread overview]
Message-ID: <20100601044813.GC13883@nokia.com> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A53043E537F75@dlee03.ent.ti.com>
On Mon, May 31, 2010 at 11:45:39PM +0200, ext Arce, Abraham wrote:
>+static struct omap4_keypad_platform_data sdp4430_keypad_data = {
>+ .keymap_data = &sdp4430_keymap_data,
>+ .rows = 8,
>+ .cols = 8,
>+ .device_enable = omap_device_enable,
>+ .device_shutdown = omap_device_shutdown,
>+ .device_idle = omap_device_idle,
again all three are undefined
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-06-01 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 21:45 [RFC] [PATCH v3 3/4] OMAP4: Keyboard board support Arce, Abraham
2010-06-01 4:48 ` Felipe Balbi [this message]
2010-06-02 12:26 ` Arce, Abraham
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=20100601044813.GC13883@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=x0066660@ti.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 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).