[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EC3E9E5.7030909@metafoo.de>
Date: Wed, 16 Nov 2011 17:50:45 +0100
From: Lars-Peter Clausen <lars@...afoo.de>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
Jonathan Cameron <jic23@...nel.org>,
Michael Hennerich <michael.hennerich@...log.com>,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
device-drivers-devel@...ckfin.uclinux.org, drivers@...log.com
Subject: Re: [PATCH 2/7] regmap: Make reg_config reg_defaults const
On 11/16/2011 05:39 PM, Mark Brown wrote:
> On Wed, Nov 16, 2011 at 05:36:20PM +0100, Lars-Peter Clausen wrote:
>> On 11/16/2011 05:24 PM, Mark Brown wrote:
>
>>> Did you actually check the sparse output?
>
>> No, because the only place we ever look at config->reg_defaults is in
>> regache_init. And now I just run sparse and as expected regmap doesn't
>> trigger any warnings or errors.
>
> CHECK drivers/base/regmap/regmap.c
> drivers/base/regmap/regmap.c:162:27: warning: incorrect type in assignment (different modifiers)
> drivers/base/regmap/regmap.c:162:27: expected struct reg_default *reg_defaults
> drivers/base/regmap/regmap.c:162:27: got struct reg_default const *const reg_defaults
Hu? which patches did you apply? If I have regmap/for-next plus patch 1 and
patch 2 of this series there isn't even a reference to reg_defaults in regmap.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists