linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Samuel Ortiz <sameo@openedhand.com>
Cc: linux-input@vger.kernel.org, Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [patch 2.6.29-rc2] input:  dm355evm_keys driver
Date: Fri, 26 Jun 2009 12:04:31 -0700	[thread overview]
Message-ID: <200906261204.31927.david-b@pacbell.net> (raw)
In-Reply-To: <20090623060604.GB14724@dtor-d630.eng.vmware.com>

On Monday 22 June 2009, Dmitry Torokhov wrote:
> 
> > > As you have noticed the driver is in mainline already;
> > 
> > Actually I didn't notice until just now.  It was moved
> > from input/keyboard to input/misc.  And I wasn't cc'd
> > on this at any point ... so it's no wonder I had no idea
> > what was happening!
> > 
> 
> Ah, sorry, it was me - all RC drivers live in input/misc,
> that's why I moved it there.

Moving it did break more than just config files ... see
the appended fixup patch.  I'll suggest that it go through
the input tree to keep things together, though if Sam wants
to take this through MFD he surely has that option.  :)

- Dave

p.s. Of course this is is a hybrid keypad-plus-remote
     driver.  :)  The only real issue here is having this
     change with no notice.

======== CUT HERE
From: David Brownell <dbrownell@users.sourceforge.net>

The keypad driver for the DM355 EVM got slightly broken as it merged,
since it moved from input/keyboard to input/misc and its Kconfig
symbol changed.  This patch copes with the changed Kconfig symbol.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
---
 drivers/mfd/dm355evm_msp.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

--- a/drivers/mfd/dm355evm_msp.c
+++ b/drivers/mfd/dm355evm_msp.c
@@ -32,8 +32,7 @@
  * This driver was tested with firmware revision A4.
  */
 
-#if defined(CONFIG_KEYBOARD_DM355EVM) \
-		|| defined(CONFIG_KEYBOARD_DM355EVM_MODULE)
+#if defined(CONFIG_INPUT_DM355EVM) || defined(CONFIG_INPUT_DM355EVM_MODULE)
 #define msp_has_keyboard()	true
 #else
 #define msp_has_keyboard()	false

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-26 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 21:15 [patch 2.6.29-rc2] input: dm355evm_keys driver David Brownell
2009-04-21  6:19 ` David Brownell
2009-06-22  0:10   ` David Brownell
2009-06-23  5:05     ` Dmitry Torokhov
2009-06-23  5:40       ` David Brownell
2009-06-23  6:06         ` Dmitry Torokhov
2009-06-24 17:18           ` David Brownell
2009-06-26 19:04           ` David Brownell [this message]
2009-06-30  2:32             ` Dmitry Torokhov
2009-06-23 14:59         ` Kevin Hilman
2009-06-24 17:21       ` [patch 2.6.30] input: dm355evm_keys uses threaded IRQs David Brownell
2009-06-30  2:32         ` Dmitry Torokhov
2009-06-22  0:39   ` [RESEND/x3 patch 2.6.30] input: dm355evm_keys driver David Brownell

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=200906261204.31927.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-input@vger.kernel.org \
    --cc=sameo@openedhand.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).