From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH 8/8] Input: atmel-wm97xx: Use module_platform_driver_probe macro
Date: Tue, 5 Mar 2013 11:51:26 +0800 [thread overview]
Message-ID: <20130305035121.GD9391@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAK9yfHx-v0B=QXvTzGUndDMroQg3nD8artGFOxfXCKf7u_P+8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
On Tue, Mar 05, 2013 at 09:17:27AM +0530, Sachin Kamat wrote:
> On 5 March 2013 09:06, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> >I know the existing code does this, it's not
> > clear to me that that's a good idea either.
> However, if your question is why return platform_driver_probe() at all
> instead of platform_driver_register() in the first place, then I am
> sorry I do not have much idea about it.
Yes, I'm questioning if this is the right cleanup to do.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-05 3:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 3:23 [PATCH 1/8] Input: davinci_keyscan: Use module_platform_driver_probe macro Sachin Kamat
2013-03-05 3:23 ` [PATCH 2/8] Input: twl4030-pwrbutton: " Sachin Kamat
2013-03-05 3:23 ` [PATCH 3/8] Input: amikbd: Use " Sachin Kamat
2013-03-05 3:23 ` [PATCH 4/8] Input: nomadik-ske-keypad: " Sachin Kamat
2013-03-07 4:16 ` Linus Walleij
2013-03-05 3:23 ` [PATCH 5/8] Input: amimouse: " Sachin Kamat
2013-03-05 3:23 ` [PATCH 6/8] Input: at32psif: " Sachin Kamat
2013-03-05 3:23 ` [PATCH 7/8] Input: q40kbd: " Sachin Kamat
2013-03-05 3:23 ` [PATCH 8/8] Input: atmel-wm97xx: " Sachin Kamat
2013-03-05 3:36 ` Mark Brown
2013-03-05 3:47 ` Sachin Kamat
2013-03-05 3:51 ` 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=20130305035121.GD9391@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sachin.kamat@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.