public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: Paul Parsons <lost.distance@yahoo•com>,
	haojian.zhuang@gmail•com, linux-next@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v2] ARM: pxa: fix regulator related build fail in magician_defconfig
Date: Wed, 7 Mar 2012 14:57:17 +0000	[thread overview]
Message-ID: <20120307145717.GN3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F5774B0.1030209@windriver.com>

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

On Wed, Mar 07, 2012 at 09:46:08AM -0500, Paul Gortmaker wrote:

> Thanks for the report.  The regulator code is rather foreign
> to me, but I think I figured out the expectations on the names
> last night when looking at a similar patch here:

All it's looking for is the output of dev_name() for the device.

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

  reply	other threads:[~2012-03-07 14:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 19:46 [PATCH] ARM: pxa: fix regulator related build fail in magician_defconfig Paul Gortmaker
2012-03-06 20:01 ` Mark Brown
2012-03-06 20:49   ` [PATCH v2] " Paul Gortmaker
2012-03-07  1:46     ` Paul Parsons
2012-03-07 14:46       ` Paul Gortmaker
2012-03-07 14:57         ` Mark Brown [this message]
2012-03-08 21:34       ` [PATCH] " Paul Gortmaker
2012-03-09  2:47         ` Paul Parsons
2012-03-14  8:38         ` Haojian Zhuang
2012-03-14 12:30           ` Paul Gortmaker
2012-03-14 12:32             ` Mark Brown
2012-03-28  9:43               ` Russell King - ARM Linux
2012-03-28 10:18                 ` Mark Brown
2012-03-28 13:36                   ` Haojian Zhuang
2012-03-28 17:56                   ` Russell King - ARM Linux
2012-03-28 18:10                     ` 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=20120307145717.GN3107@opensource.wolfsonmicro.com \
    --to=broonie@opensource$(echo .)wolfsonmicro.com \
    --cc=haojian.zhuang@gmail$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lost.distance@yahoo$(echo .)com \
    --cc=paul.gortmaker@windriver$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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