All of lore.kernel.org
 help / color / mirror / Atom feed
From: cbouatmailru@gmail.com (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [V4 3/4] power_supply: Enable battery-charger for 88pm860x
Date: Fri, 21 Sep 2012 15:39:15 -0700	[thread overview]
Message-ID: <20120921223913.GA25603@lizard> (raw)
In-Reply-To: <20120921221422.GA28670@sortiz-mobl>

On Sat, Sep 22, 2012 at 12:14:22AM +0200, Samuel Ortiz wrote:
> > > >> Thanks for helping me to amend these patch.  I got many good
> > > >> suggestions and learn a lot in this process:) BTW, you mean you will
> > > >> help to amend that several minor warning with battery tree?
> > > >
> > > > Yup, I have these small fixups locally in my tree already, so if/once
> > > > Samuel gives me an Ack for the mfd part, I'll merge it into battery git
> > > > tree.
> > > 
> > > Any updates?
> > 
> > OK, I guess I can just go ahead and apply it, the MFD changes are very
> > trivial anyway. So, this is now applied (along with some fixups that
> > I was talking about in my previous reply).
> Applying this patch as is will not build as the mfd_add_devices() API has
> changed. Either you rebase your patchset on top of Linus tree or I take this
> patch and fix the mfd_add_devices() call. Please let me know how you want to
> proceed.

It's not the first time this happens, and git let us fix it in a pretty
elegant way: what I'm usually doing is just pulling Linus' tree back into
my tree (but not rebasing), and in the merge commit I fixup the issue.
That way things are still bisectable, and everything should work before
and after mfd_add_devices() change.

So, it's all OK, I'll just merge Linus' -rc6 back into my tree
(and Stephen already has a fix in linux-next).

Thanks!
Anton.

  reply	other threads:[~2012-09-21 22:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  6:18 [V2 1/3] regulator: add pre-regulator support for 88pm860x Jett.Zhou
2012-06-21 10:15 ` Mark Brown
2012-06-21 11:31   ` [V3 " Jett.Zhou
2012-06-21 22:54     ` Mark Brown
2012-07-05 14:24     ` Samuel Ortiz
2012-07-05 14:15       ` Mark Brown
2012-07-06  1:59         ` jett zhou
2012-07-06  2:58         ` [V3 1/4] regulator: 88pm860x: add pre-regulator support for 88pm860x regulator Jett.Zhou
2012-09-13  7:47           ` Haojian Zhuang
2012-07-06  2:59         ` [V3 2/4] mfd: 88pm860x: add pre-regulator device for 88pm860x Jett.Zhou
2012-07-06  9:01           ` Samuel Ortiz
2012-07-06  3:02         ` [V3 3/4] power_supply: Enable battery-charger " Jett.Zhou
2012-07-14  8:12           ` Anton Vorontsov
2012-07-16  5:27             ` jett zhou
2012-07-27  8:28             ` [V4 " Jett.Zhou
2012-08-23  3:48               ` Anton Vorontsov
2012-08-23  4:43                 ` Anton Vorontsov
2012-08-23  9:06                   ` jett zhou
2012-08-23 12:22                     ` Anton Vorontsov
2012-08-23 12:26                       ` jett zhou
2012-09-13  7:48                       ` Haojian Zhuang
2012-09-20 22:35                         ` Anton Vorontsov
2012-09-21  1:01                           ` Haojian Zhuang
2012-09-21 22:14                           ` Samuel Ortiz
2012-09-21 22:39                             ` Anton Vorontsov [this message]
2012-07-06  3:02         ` [V3 4/4] ARM: MMP: add 88pm860x battery-charger support Jett.Zhou

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=20120921223913.GA25603@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.