All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Sachin Kamat <sachin.kamat@samsung.com>,
	Mark Brown <broonie@linaro.org>,
	Sangbeom Kim <sbkim73@samsung.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Idea: regulator: Merge s2mpa01 with s2mps11
Date: Mon, 05 May 2014 10:56:41 +0200	[thread overview]
Message-ID: <1399280201.17696.6.camel@AMDC1943> (raw)
In-Reply-To: <CAK9yfHwge_4HFzqj+4kgcY+fQTy1uQBp-=RhyX2YYRt3hKLPXA@mail.gmail.com>

On śro, 2014-04-30 at 20:57 +0530, Sachin Kamat wrote:
> Hi Krzysztof,
> 
> On 30 April 2014 18:56, Krzysztof Kozlowski <k.kozlowski@samsung.com> wrote:
> > Dear Sachin,
> >
> >
> > The S2MPA01 and S2MPS1X PMICs regulator drivers look quite similar to
> > each other. Most of the S2MPA01 driver is the same as S2MPS11 (except
> > changes added for supporting S2MPS14).
> >
> > I would like to merge these drivers into one. However I do not have
> > neither any board with S2MPA01 nor S2MPA01 datasheet.
> >
> > What do you think about merging them?
> 
> It is a good idea to merge them. That was my initial plan too.
> I appreciate your offer to do the same.
> 
> >Could you test it later when I will finish the development?
> 
> I will not be able to do it immediately though as currently I am involved
> with some other activity on a different h/w and will be on vacation for some
> time later next week onwards.

It is not an urgent task. I'll let you know when I got some working
solution.

Best regards,
Krzysztof


      reply	other threads:[~2014-05-05  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 13:26 Idea: regulator: Merge s2mpa01 with s2mps11 Krzysztof Kozlowski
2014-04-30 15:27 ` Sachin Kamat
2014-05-05  8:56   ` Krzysztof Kozlowski [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=1399280201.17696.6.camel@AMDC1943 \
    --to=k.kozlowski@samsung.com \
    --cc=broonie@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=sachin.kamat@samsung.com \
    --cc=sbkim73@samsung.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 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.