[alsa-devel] ASOC deprecated warning
What's the status of this?
CC sound/soc/soc-dapm.o sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is deprecated (declared at sound/soc/soc-dapm.c:1026) sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is deprecated (declared at sound/soc/soc-dapm.c:1026)
Could we have a Kconfig option of disabling deprecated APIs? If I can get rid of this I'll have a warning free build.
On Thu, Oct 30, 2008 at 03:22:31PM -0400, Jon Smirl wrote:
What's the status of this?
Could we have a Kconfig option of disabling deprecated APIs? If I can get rid of this I'll have a warning free build.
The API is removed in ALSA git, you can cherry pick the patch over if you want. Otherwise I'd suggest taking it up with the people maintaining the compiler infrastructure - there's no way to warn on use of an API without also warning on the export of the API, which isn't ideal.
On Thu, Oct 30, 2008 at 3:51 PM, Mark Brown broonie@sirena.org.uk wrote:
On Thu, Oct 30, 2008 at 03:22:31PM -0400, Jon Smirl wrote:
What's the status of this?
Could we have a Kconfig option of disabling deprecated APIs? If I can get rid of this I'll have a warning free build.
The API is removed in ALSA git, you can cherry pick the patch over if you want. Otherwise I'd suggest taking it up with the people maintaining the compiler infrastructure - there's no way to warn on use of an API without also warning on the export of the API, which isn't ideal.
sysfs has a config attribute for including legacy APIs. If it isn't set they compile out.
At Thu, 30 Oct 2008 15:57:33 -0400, Jon Smirl wrote:
On Thu, Oct 30, 2008 at 3:51 PM, Mark Brown broonie@sirena.org.uk wrote:
On Thu, Oct 30, 2008 at 03:22:31PM -0400, Jon Smirl wrote:
What's the status of this?
Could we have a Kconfig option of disabling deprecated APIs? If I can get rid of this I'll have a warning free build.
The API is removed in ALSA git, you can cherry pick the patch over if you want. Otherwise I'd suggest taking it up with the people maintaining the compiler infrastructure - there's no way to warn on use of an API without also warning on the export of the API, which isn't ideal.
sysfs has a config attribute for including legacy APIs. If it isn't set they compile out.
The functions will be removed in 2.6.29. No further work needed.
Takashi
On Thu, Oct 30, 2008 at 03:57:33PM -0400, Jon Smirl wrote:
On Thu, Oct 30, 2008 at 3:51 PM, Mark Brown broonie@sirena.org.uk wrote:
you want. Otherwise I'd suggest taking it up with the people maintaining the compiler infrastructure - there's no way to warn on use of an API without also warning on the export of the API, which isn't ideal.
sysfs has a config attribute for including legacy APIs. If it isn't set they compile out.
As I suggested, if you'd like to see a similar configuration option for deprecated APIs the best people to take it up with would probably be the people who maintain the compiler infrastructure which is used to generate the deprecation warning so we can have something central for this.
participants (3)
-
Jon Smirl -
Mark Brown -
Takashi Iwai