27 Jun
2012
27 Jun
'12
11:44 a.m.
On Wed, Jun 27, 2012 at 01:39:52PM +0200, Takashi Iwai wrote:
Mark Brown wrote:
It's fixed in -next, not in for-3.5. I guess I'll pick the change over at some point.
Ideally, such a problem should have been fixed for 3.5 by just removing const, and add const again once after ASoC core is changed for 3.6. But I've been ignoring this warning since it's certainly no big issue.
The fix in -next is to remove the const, it's not simply a case of adding the const in the core as we currently fiddle with the ops structs to add default ops (which we shouldn't do).