linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code
Date: Fri, 28 Nov 2014 16:48:39 +0000	[thread overview]
Message-ID: <20141128164839.GV3836@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1417189984.4371.12.camel@arm.com>

On Fri, Nov 28, 2014 at 03:53:04PM +0000, Pawel Moll wrote:
> To summarize, I believe that setting CONFIG_REGULATOR=y (as in
> vexpress_defconfig) should solve your issue.

It does, thanks.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

      parent reply	other threads:[~2014-11-28 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 18:17 [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code Pawel Moll
2014-11-25 18:17 ` [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform Pawel Moll
2014-11-26  1:54   ` Mike Turquette
2014-11-26  1:59     ` Joe Perches
2014-11-26 12:04       ` Pawel Moll
2014-11-26 12:17         ` Arnd Bergmann
2014-11-26 14:40           ` Pawel Moll
2014-11-26 15:40             ` Joe Perches
2014-11-26 12:13   ` [PATCH v2] " Pawel Moll
2014-11-28 15:14     ` Arnd Bergmann
2014-11-28 17:56     ` Joe Perches
2014-12-01 13:57       ` Pawel Moll
2014-12-01 14:16         ` [PATCH] MAINTAINERS: ARM Versatile Express platform, add missing pattern Pawel Moll
2014-12-04 16:02           ` Arnd Bergmann
2014-11-28 15:08 ` [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code Arnd Bergmann
2014-11-28 15:30   ` Russell King - ARM Linux
2014-11-28 15:53     ` Pawel Moll
2014-11-28 16:31       ` Arnd Bergmann
2014-11-28 16:34         ` Pawel Moll
2014-11-28 16:44           ` [PATCH RESEND] ARM: vexpress: Enable regulator framework when MMCI is in use Pawel Moll
2014-11-28 20:57             ` Arnd Bergmann
2014-11-28 16:48       ` Russell King - ARM Linux [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=20141128164839.GV3836@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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).