public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Chao Xie <cxie4@marvell.com>
Cc: Axel Lin <axel.lin@ingics.com>, Yi Zhang <yizhang@marvell.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register
Date: Mon, 1 Jul 2013 09:46:20 +0100	[thread overview]
Message-ID: <20130701084620.GU27646@sirena.org.uk> (raw)
In-Reply-To: <AAD1C6EB06EE3649B35B7E026785068D2581736992@SC-VEXCH2.marvell.com>

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

On Sun, Jun 30, 2013 at 07:14:55PM -0700, Chao Xie wrote:

Please fix your mailer to word wrap within paragraphs.

> I have seen that mfd: 88pm800: add regulator sub device is already
> merged into Linux-next. So you mean that I need wait for 3.11 to
> release, then resubmit the regulator patch?

Yes, that should be fine.

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

  reply	other threads:[~2013-07-01  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 13:32 [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register Axel Lin
2013-06-28 13:34 ` [PATCH 2/2] regulator: 88pm800: Remove NULL test for regulator_unregister() Axel Lin
2013-06-28 13:50 ` [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register Mark Brown
2013-07-01  2:14   ` Chao Xie
2013-07-01  8:46     ` Mark Brown [this message]
2013-07-01  8:46     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2013-07-19  1:16 Axel Lin
2013-07-19 17:24 ` Mark Brown

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=20130701084620.GU27646@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=axel.lin@ingics.com \
    --cc=cxie4@marvell.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yizhang@marvell.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