linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Rename keypad and ts platform driver for w90p910
Date: Mon, 17 Aug 2009 22:25:07 -0700	[thread overview]
Message-ID: <20090818055620.73F65526EA5@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <e68bb3470908170144w49cf2e44g56eba456424a9a4b@mail.gmail.com>

Hi Wan,

On Mon, Aug 17, 2009 at 04:44:03PM +0800, Wan ZongShun wrote:
> Dear Dmitry,
> 
> Sir, Due to only w90p910 was renamed, other CPUs of the series
> originally was named after NUC9xx,
> the ts and keypad was public use by w90p910 ,nuc950 and nuc920,

OK, I see.

 so, if
> the 'w90p910-ts' and 'w90p910-keypad' could not be renamed ,I have to
> make the platform device names of nuc920 and nuc960 named after
> 'w90p910-ts' and 'w90p910-keypad' too, Hmm, I think it is so confused.

May I suggest calling the driver/devices nuc9xx-ts and nuc9xx-ts? Then
you should have some wiggle room. Also I think you should push out the
patches changing driver names together with your platform code (and not
through subsystem trees), otheriwse there will be a period when drivers
stop binding to your devices. Just make sure you get Acks from the
maintainers and you should be set.

And please adjust the Kconfig entries to mention the other chipsets as
well.

-- 
Dmitry

  reply	other threads:[~2009-08-18  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17  3:55 [PATCH] input: Rename keypad and ts platform driver for w90p910 Wan ZongShun
2009-08-17  8:17 ` Dmitry Torokhov
2009-08-17  8:44   ` Wan ZongShun
2009-08-18  5:25     ` Dmitry Torokhov [this message]
2009-08-18  6:13       ` Wan ZongShun

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=20090818055620.73F65526EA5@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=mcuos.com@gmail.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).