From: Philipp Zabel <p.zabel@pengutronix.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] regmap: default Y if REGMAP_MMIO is selected
Date: Wed, 17 Oct 2012 14:33:31 +0200 [thread overview]
Message-ID: <1350477211.2603.49.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <20121017123226.GM14199@opensource.wolfsonmicro.com>
Am Mittwoch, den 17.10.2012, 21:32 +0900 schrieb Mark Brown:
> On Wed, Oct 17, 2012 at 02:31:16PM +0200, Philipp Zabel wrote:
> > The syscon mfd driver selects REGMAP_MMIO and uses struct regmap_config,
> > which is only defined if CONFIG_REGMAP is enabled.
>
> Already fixed by someone else, can't remember who now. Will send to
> Linus soon.
Great, thanks.
regrads
Philipp
prev parent reply other threads:[~2012-10-17 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:31 [PATCH] regmap: default Y if REGMAP_MMIO is selected Philipp Zabel
2012-10-17 12:32 ` Mark Brown
2012-10-17 12:33 ` Philipp Zabel [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=1350477211.2603.49.camel@pizza.hi.pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).