linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sangbeom Kim <sbkim73@samsung.com>
To: "'Samuel Ortiz'" <sameo@linux.intel.com>
Cc: "'Mark Brown'" <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org, "'Liam Girdwood'" <lrg@ti.com>,
	sbkim01@gmail.com
Subject: RE: [PATCH V2 0/7] Initial release of Samsung S2MPS11 pmic driver
Date: Tue, 10 Jul 2012 11:02:46 +0900	[thread overview]
Message-ID: <008201cd5e40$197c5930$4c750b90$@com> (raw)
In-Reply-To: <20120709111308.GL15345@sortiz-mobl>

Hi!
On Mon, Jul 09, 2012 at 08:13PM +0900, Samuel Ortiz wrote:
> Hi Sangbeom,
> 
> On Sat, Jul 07, 2012 at 06:39:12PM +0900, Sangbeom Kim wrote:
> > The S2MPS11 is comprised of high efficient Buck converters,
> > various LDOs, and an RTC and tightly coupled with Multi Core Samsung
> > Application Processors, which is used in a wide variety of mobile applications
> > such as smart phones and tablet PCs.
> > S2MPS11 provide 10 high efficiency buck converters and 38 LDO regulators.
> > Especially, Buck2 can support 7.0A current capacity for high performance
> > samsung application processor.
> > Most of S2MPS11 feature are similar to S5M series.
> > and Instead of using s5m prefix, Samsung decide to use s2m prefix.
> > So, I try to make common mfd driver for S2M and S5M series.
> > Most of s5m prefix is changed into sec prefix.
> >
> > Changes since V1:
> > 1. Replace list_voltage with standard framework
> > 2. Apply regmap_irq
> > 3. Minor changes.
> I was trying to apply this patchset to my for-next branch, but it doesn't
> apply properly.
> Could you please rebase it against this branch and send it to me ?
> 
> Cheers,
> Samuel.

Sorry, After rebase it, I will send again.

Thanks,
Sangbeom.


      reply	other threads:[~2012-07-10  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07  9:39 [PATCH V2 0/7] Initial release of Samsung S2MPS11 pmic driver Sangbeom Kim
2012-07-09 11:13 ` Samuel Ortiz
2012-07-10  2:02   ` Sangbeom Kim [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='008201cd5e40$197c5930$4c750b90$@com' \
    --to=sbkim73@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=sbkim01@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;
as well as URLs for NNTP newsgroup(s).