mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
	linux-input@vger.kernel.org, broonie@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
	myungjoo.ham@samsung.com
Subject: Re: [PATCH v3 2/2] input: add driver support for MAX8997-haptic
Date: Fri, 16 Mar 2012 12:27:35 -0700	[thread overview]
Message-ID: <20120316192735.GA19351@core.coreip.homeip.net> (raw)
In-Reply-To: <20120316185626.GO20524@sortiz-mobl>

On Fri, Mar 16, 2012 at 07:56:26PM +0100, Samuel Ortiz wrote:
> Hi Dmitry,
> 
> On Fri, Mar 16, 2012 at 10:55:24AM -0700, Dmitry Torokhov wrote:
> > > > OK, excellent. I'll pick up this fix and apply the driver for 3.4 queue,
> > > > thanks!
> > > Your patch depends on the MFD changes Choi sent along the input driver. I
> > > think it would make more sense for me to take it. What do you think ?
> > 
> > I think that splitting required platform data definitions from the
> > driver into separate patch is quite pointless. 
> Hmm, you're right on this one.
> 
> > I often see a driver
> > split in 3+ patches - headers, the driver itself and Kconfig/makefile
> > changes and I wonder what made them do it...
> > 
> > Anyway, below is the consolidated patch I was going to apply to my tree,
> > but if you want to go through yours - feel free to apply it.
> No, I think it makes sense for you to take it. Add my:
> Acked-by: Samuel Ortiz <sameo@linux.intel.com>
> 
> if you feel it's needed.

I will, thank you.

-- 
Dmitry

      reply	other threads:[~2012-03-16 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12  8:31 Chanwoo Choi
2012-03-14  8:46 ` Dmitry Torokhov
2012-03-14 11:54   ` Chanwoo Choi
2012-03-14 14:47   ` Chanwoo Choi
2012-03-14 15:48     ` Dmitry Torokhov
2012-03-16 17:48       ` Samuel Ortiz
2012-03-16 17:55         ` Dmitry Torokhov
2012-03-16 18:56           ` Samuel Ortiz
2012-03-16 19:27             ` Dmitry Torokhov [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=20120316192735.GA19351@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=sameo@linux.intel.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

all inboxes | Powered by JetHome®