linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Miguel Aguilar <miguel.aguilar@ridgerun.com>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	"clark.becker@ridgerun.com" <clark.becker@ridgerun.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"santiago.nunez@ridgerun.com" <santiago.nunez@ridgerun.com>,
	"todd.fischer@ridgerun.com" <todd.fischer@ridgerun.com>
Subject: Re: [PATCH v3 1/2] Input: Add DaVinci DM365 Keypad support
Date: Tue, 22 Sep 2009 20:46:27 -0700	[thread overview]
Message-ID: <20090923034627.GA1458@core.coreip.homeip.net> (raw)
In-Reply-To: <871vlyev8g.fsf@deeprootsystems.com>

On Tue, Sep 22, 2009 at 10:37:35AM -0700, Kevin Hilman wrote:
> Miguel Aguilar <miguel.aguilar@ridgerun.com> writes:
> 
> > Sekhar,
> >
> > If you and Sneha agree I will write driver in terms of davinci instead of dm365.
> >
> 
> I add a vote the davinci* naming instead of dm365*.
> 

Can you guarantee that this will be the only keypad implementation for
davinci? If not then I'd say using base model number and updating
Kconfig text is fine.

-- 
Dmitry

  reply	other threads:[~2009-09-23  3:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 20:06 [PATCH v3 1/2] Input: Add DaVinci DM365 Keypad support miguel.aguilar
2009-09-18  5:35 ` Nori, Sekhar
2009-09-18 14:32   ` Miguel Aguilar
2009-09-22  7:05     ` Nori, Sekhar
2009-09-22 14:01       ` Miguel Aguilar
2009-09-22 17:37         ` Kevin Hilman
2009-09-23  3:46           ` Dmitry Torokhov [this message]
2009-09-23  6:20             ` Nori, Sekhar
2009-09-23 14:58               ` Miguel Aguilar
2009-09-23 15:13                 ` Nori, Sekhar

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=20090923034627.GA1458@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=clark.becker@ridgerun.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-input@vger.kernel.org \
    --cc=miguel.aguilar@ridgerun.com \
    --cc=nsekhar@ti.com \
    --cc=santiago.nunez@ridgerun.com \
    --cc=todd.fischer@ridgerun.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).