[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120718100013.GC22739@opensource.wolfsonmicro.com>
Date: Wed, 18 Jul 2012 11:00:13 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: "AnilKumar, Chimata" <anilkumar@...com>
Cc: "rdunlap@...otime.net" <rdunlap@...otime.net>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: Re: [PATCH] regulator: tps65217: fix build error if REGULATOR is not
enabled
On Wed, Jul 18, 2012 at 09:55:57AM +0000, AnilKumar, Chimata wrote:
> Regulators platform data is added to platform device in MFD driver, which we
> need for regulator driver, of_regulator_match() is used to check the regulator
> consumers if we pass DT data. If we do not enable CONFIG_REGULATOR then
> of_regulator_match() is not exported, so we see this error.
Why are you doing that in the MFD driver?
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists