From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jiri Slaby <jirislaby@gmail.com>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] New include file for marking old style api files
Date: Thu, 28 Jul 2005 16:25:00 +0200 [thread overview]
Message-ID: <20050728142500.GA26706@lug-owl.de> (raw)
In-Reply-To: <42E8E6BD.90807@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Thu, 2005-07-28 16:07:57 +0200, Jiri Slaby <jirislaby@gmail.com> wrote:
> Adrian Bunk napsal(a):
> >What's wrong with __deprecated ?
> >
> >
> Nothing, but this marks entire driver, not a function, that it uses.
> I.e. gazel doesn't emit any warning or so, I think; so for these cases.
So what's actually wrong with the gazel driver? I'm not an user or
author of it.
When it's the use of old APIs, I indeed think that __deprecated is
exactly what we want. If a driver is superseded by a different one (OSS
vs. ALSA, eepro100 vs e100, ...), sticking a #warning or #error right
into the driver (and not into an included header file) looks quite right
to me.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Buerger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-28 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:42 [PATCH] New include file for marking old style api files Jiri Slaby
2005-07-28 13:50 ` Jiri Slaby
2005-07-28 13:56 ` John W. Linville
2005-07-28 14:02 ` Adrian Bunk
2005-07-28 14:07 ` Jiri Slaby
2005-07-28 14:25 ` Jan-Benedict Glaw [this message]
2005-07-28 14:32 ` Adrian Bunk
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=20050728142500.GA26706@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=bunk@stusta.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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