From: Arnd Bergmann <arnd@arndb.de>
To: MyungJoo Ham <myungjoo.ham@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Mike Lockwood" <lockwood@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Donggeun Kim" <dg77.kim@samsung.com>, "Greg KH" <gregkh@suse.de>,
"Grant Likely" <grant.likely@secretlab.ca>,
"Kalle Komierowski" <karl.komierowski@stericsson.com>,
"Johan PALSSON" <johan.palsson@stericsson.com>,
"Daniel WILLERUD" <daniel.willerud@stericsson.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>
Subject: Re: [RFC PATCH 0/3] introduce: Multistate Switch Class
Date: Tue, 29 Nov 2011 13:59:58 +0000 [thread overview]
Message-ID: <201111291359.59103.arnd@arndb.de> (raw)
In-Reply-To: <CAJ0PZbT8FcCq=6GzLxOhhpRvCbCaJJEhE9_2GXXT4P0XZp6H-w@mail.gmail.com>
On Tuesday 29 November 2011, MyungJoo Ham wrote:
> For the next iteration, I'm considering the followings. It'd be much
> appreciated if I could get some comments about those beforehand.
>
> 2. move the location from /drivers/misc to an independent location.
> /drivers/switch? /drivers/multistate-switch? /drivers/msc?
> /drivers/mswitch? ...
Moving out of drivers/misc is a good idea. I don't have a strong
preference for any of the alternatives, but would probably pick
drivers/mswitch. drivers/switch is too generic, since we have lots
of things that are called a switch already, and drivers/multistate-switch
is much longer than any of the other alternatives. "msc" in turn
seems a bit too short and is not a well-established acronym yet.
Arnd
next prev parent reply other threads:[~2011-11-29 14:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 2:03 MyungJoo Ham
2011-11-25 14:02 ` Arnd Bergmann
2011-11-26 5:46 ` MyungJoo Ham
2011-11-26 13:23 ` Kyungmin Park
2011-11-27 22:43 ` Linus Walleij
2011-11-27 23:08 ` Greg KH
2011-11-28 0:09 ` Dmitry Torokhov
2011-11-28 0:19 ` Greg KH
2011-11-28 9:03 ` Dmitry Torokhov
2011-11-28 1:31 ` NeilBrown
2011-11-28 7:27 ` Greg KH
2011-11-28 9:04 ` Dmitry Torokhov
2011-11-30 6:35 ` Greg KH
2011-11-30 6:58 ` MyungJoo Ham
2011-11-30 9:46 ` Mark Brown
2011-11-30 13:28 ` Linus Walleij
2011-11-30 23:04 ` NeilBrown
2011-12-01 13:38 ` Linus Walleij
2011-11-28 13:04 ` Linus Walleij
2011-11-28 15:09 ` Morten CHRISTIANSEN
2011-11-30 6:34 ` Greg KH
2011-11-28 17:53 ` Arnd Bergmann
2011-11-29 9:11 ` MyungJoo Ham
2011-11-29 9:45 ` Linus Walleij
2011-11-29 13:59 ` Arnd Bergmann [this message]
2011-11-29 17:05 ` Dmitry Torokhov
2011-11-30 2:58 ` NeilBrown
2011-11-30 6:40 ` MyungJoo Ham
2011-11-30 22:56 ` NeilBrown
2011-11-30 23:17 ` Mark Brown
2011-11-30 23:25 ` Dmitry Torokhov
2011-12-01 4:51 ` MyungJoo Ham
2011-12-01 5:21 ` NeilBrown
2011-12-01 11:34 ` Mark Brown
2011-12-05 3:04 ` NeilBrown
2011-12-05 12:06 ` Mark Brown
2011-12-05 19:38 ` NeilBrown
2011-12-05 19:45 ` Mark Brown
2011-12-01 4:46 ` MyungJoo Ham
2011-12-07 9:31 ` Linus Walleij
2011-12-08 4:42 ` Kyungmin Park
2011-11-26 15:32 ` Greg KH
2011-11-29 8:18 ` MyungJoo Ham
2011-11-28 18:23 ` Mark Brown
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=201111291359.59103.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arve@android.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=daniel.willerud@stericsson.com \
--cc=dg77.kim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=johan.palsson@stericsson.com \
--cc=karl.komierowski@stericsson.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lockwood@android.com \
--cc=myungjoo.ham@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
Powered by JetHome