From: Hauke Mehrtens <hauke@hauke-m.de>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: build error with CONFIG_REGMAP=m and CONFIG_REGULATOR=y
Date: Sun, 17 Nov 2013 17:00:38 +0100 [thread overview]
Message-ID: <5288E826.7050204@hauke-m.de> (raw)
In-Reply-To: <20131117152721.GA20266@sirena.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/17/2013 04:27 PM, Mark Brown wrote:
> On Sun, Nov 17, 2013 at 04:06:45PM +0100, Hauke Mehrtens wrote:
>
>> In OpenWrt we are seeing some build errors when CONFIG_REGMAP=m
>> and CONFIG_REGULATOR=y are set.
>
> REGMAP is a bool config option, it should not be possible to set it
> to m. How have you managed to do that?
>
Sorry, I you are right, I just saw we have a patch applied on top of
the mainline kernel which makes it possible to build REGMAP as module.
Hauke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSiOgfAAoJEIZ0px9YPRMygR4P/inb+qZKSSA7qloN2ipKasbC
mDKV/LivY6l3Je+rWTRCESkGOw0jO09rO1AizCoUN47u6yYuC6/IGIPioDXTciFf
iDl46Lhfirv3rlWyrQTC6ZAAxcQUzFJNgXD0hb+ehw3MBC9okB5NQgq9QATtpW9L
Bbu7vCgqG7bxCXXq0DW/ygPMR5axKWQwbQdDCfz+06wYqWQqj2okWtHvhXCe7Skb
ROZ8FvOcnXKKjoGOEJRtbcfUt44dIM8RGJtKj5vjXtnSm+eJQhL1OzqUxOY7OODW
Fxqs97N7rrsPVwXNRYSrHjtmul3feLUaxALXQiSskjS8zJsJBgR9jGJjMp2auN5B
4ffxa0+thFsSNSXQd2bfDPnZzZKZf2EWr3h0BqWZPjN60pIji/WUXMSecVd+9zNH
axONP2lKOp0hPxsSi0hvLUGHAyAsOTzShPKjV+vIosb9aFn5/3GeQqOrY6abmF/1
HPoIds00q2B9VVV83PQeLvMFhjcW++1HDhP7QJ+QiUByN9I96M1Awd27ypsf5PT/
fKqIgumJk2Jy3rKmpOwMHlpONBhD39qW3tb9lmiXeWgAdvaSH/kuR5Lwsbe3vhvg
p+hTwmubGTwFHaIKUD7APJk7daYUwR8VEP3fbwsYc3bCGMtN61FNyl5HymYteJMg
0g4dQrXMaPTZJcMTp4nz
=LoHr
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-11-17 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 15:06 Hauke Mehrtens
2013-11-17 15:27 ` Mark Brown
2013-11-17 16:00 ` Hauke Mehrtens [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=5288E826.7050204@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®