public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Jaewon Kim <jaewon02.kim@samsung.com>
Subject: Re: [PATCH 0/4] Input: Merge max77843 haptic driver into max77693
Date: Wed, 29 Jul 2015 10:08:31 -0700	[thread overview]
Message-ID: <20150729170831.GA23178@dtor-ws> (raw)
In-Reply-To: <1438151490-13751-1-git-send-email-k.kozlowski@samsung.com>

On Wed, Jul 29, 2015 at 03:31:26PM +0900, Krzysztof Kozlowski wrote:
> Hi,
> 
> 
> Description
> ===========
> The Maxim 77843 haptic driver differs from 77693 by:
> 1. Setting the bias.
> 2. Different configuration register.
> 3. Not enabling the low-sys DAC.
> 4. Using same regmap for PMIC and haptic blocks.
> 
> The patchset merges max77843 driver into the max77693.
> 
> 
> Dependencies
> ============
> The patchset *depends on* "regulator: Merge max77843 into max77693" [0]
> which was applied by Mark Brown (regulator tree). The mentioned
> regulator patchset actually changed also MFD drivers and other headers
> so the child drivers (like max77693 regulator or haptic) can be used
> with both max77693 and max77843 main MFD drivers.
> 
> 
> Merging ideas
> =============
> 0. Patches 1 and 2 can be applied directly.
> For rest of it (patches 3 and 4):
> 1. If this will go to v4.3, then maybe Mark Brown could prepare
>    an immutable branch (or a tag) with the [0] patchset?
> 2. If this will go to v4.4, then patchset can wait till MFD/regulator
>    changes reach Linus' tree.

How about 3: Mark merges it through his tree with:

Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

for the series?

Thanks!

-- 
Dmitry

  parent reply	other threads:[~2015-07-29 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  6:31 [PATCH 0/4] Input: Merge max77843 haptic driver into max77693 Krzysztof Kozlowski
2015-07-29  6:31 ` [PATCH 1/4] Input: max77693: Remove a read-only pwm_divisor field Krzysztof Kozlowski
2015-07-29  6:31 ` [PATCH 2/4] Input: max77693: Prepare for adding support for Maxim 77843 Krzysztof Kozlowski
2015-07-29  6:31 ` [PATCH 3/4] Input: max77693: Add " Krzysztof Kozlowski
2015-07-29  6:31 ` [PATCH 4/4] Input: Remove the max77843 haptic driver Krzysztof Kozlowski
2015-07-29  6:55   ` Krzysztof Kozlowski
2015-07-29 17:08 ` Dmitry Torokhov [this message]
2015-07-29 23:43   ` [PATCH 0/4] Input: Merge max77843 haptic driver into max77693 Krzysztof Kozlowski

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=20150729170831.GA23178@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=broonie@kernel.org \
    --cc=jaewon02.kim@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox