devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Thomas Abraham <thomas.abraham@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, myungjoo.ham@samsung.com,
	linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
	t.figa@samsung.com, Karol Lewandowski <k.lewandowsk@samsung.com>,
	Rajendra Nayak <rnayak@ti.com>,
	Rob Herring <rob.herring@calxeda.com>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 3/3] regulator: add device tree support for max8997
Date: Mon, 26 Nov 2012 14:46:04 +0000	[thread overview]
Message-ID: <20121126144603.GL9411@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJuYYwRRauS54nt3QxyofqSyKGcJ+T_9tnjGSt60LtGOnP+ccA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

On Mon, Nov 26, 2012 at 08:13:23PM +0530, Thomas Abraham wrote:

> I tried applying this patch on the max8997 branch in your regulator
> tree. But this patch does not apply cleanly on that branch because
> commits "5eb9f2b96381" (regulator: remove use of __devexit_p),
> "a5023574d120" (regulator: remove use of __devinit) and "8dc995f56ef7"
> (regulator: remove use of __devexit) are not available on this branch
> but these commits are already in your for-next branch.

> I am not sure if it is of any help in rebasing this patch to the
> existing max8997 branch. If you could suggest on how I could prepare
> this patch so that applies cleanly for you, I could do that.

Send something against the topic branch.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-26 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23  8:03 [PATCH 0/3] regulator: max8997: minor updates and device tree support Thomas Abraham
2012-11-23  8:03 ` [PATCH 1/3] regulator: max8997: reorder buck1/2/5 dvs setup code Thomas Abraham
2012-11-24 17:56   ` Mark Brown
     [not found] ` <1353657795-1725-1-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-11-23  8:03   ` [PATCH 2/3] regulator: max8997: limit the number of dvs registers programmed in non-dvs mode Thomas Abraham
2012-11-24 17:56     ` Mark Brown
2012-11-23  8:03 ` [PATCH 3/3] regulator: add device tree support for max8997 Thomas Abraham
2012-11-24 17:59   ` Mark Brown
2012-11-24 18:16     ` Thomas Abraham
2012-11-26  9:51       ` Mark Brown
2012-11-26 13:46         ` Thomas Abraham
2012-11-26 14:11           ` Mark Brown
2012-11-26 14:43             ` Thomas Abraham
2012-11-26 14:46               ` Mark Brown [this message]
2012-11-27  8:34                 ` [PATCH] " Thomas Abraham
2012-11-27 20:05                   ` Mark Brown
2012-11-23 15:35 ` [PATCH 0/3] regulator: max8997: minor updates and device tree support Tomasz Figa

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=20121126144603.GL9411@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=k.lewandowsk@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rnayak@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=t.figa@samsung.com \
    --cc=thomas.abraham@linaro.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;
as well as URLs for NNTP newsgroup(s).