From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: Build breakage in samsung-keypad driver
Date: Tue, 15 Nov 2011 17:36:14 +0000 [thread overview]
Message-ID: <20111115173614.GI3077@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111115173509.GC15114@core.coreip.homeip.net>
On Tue, Nov 15, 2011 at 09:35:10AM -0800, Dmitry Torokhov wrote:
> On Tue, Nov 15, 2011 at 05:25:24PM +0000, Mark Brown wrote:
> > arch/arm/plat-samsung/include/plat/keypad.h:16:11: error: unable to open 'linux/input/samsung_keypad.h'
> Ahh... that explains it. I'll fix it up, sorry for the trouble.
Thanks! I'd not actually checked what the error came from, I'd just
reverted the patch.
prev parent reply other threads:[~2011-11-15 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 12:53 Build breakage in samsung-keypad driver Mark Brown
2011-11-15 17:21 ` Dmitry Torokhov
2011-11-15 17:25 ` Mark Brown
2011-11-15 17:35 ` Dmitry Torokhov
2011-11-15 17:36 ` Mark Brown [this message]
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=20111115173614.GI3077@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-input@vger.kernel.org \
/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).