From: Mark Brown <broonie@sirena.org.uk>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Re: ASOC deprecated warning
Date: Fri, 31 Oct 2008 10:41:42 +0000 [thread overview]
Message-ID: <20081031104142.GA7516@sirena.org.uk> (raw)
In-Reply-To: <9e4733910810301257t159c1b20t3a0414b55410dd7f@mail.gmail.com>
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.
prev parent reply other threads:[~2008-10-31 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 19:22 ASOC deprecated warning Jon Smirl
2008-10-30 19:51 ` Mark Brown
2008-10-30 19:57 ` Jon Smirl
2008-10-31 6:37 ` Takashi Iwai
2008-10-31 10:41 ` Mark Brown [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=20081031104142.GA7516@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=jonsmirl@gmail.com \
/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