From: Adrian Bunk <bunk@stusta.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New include file for marking old style api files
Date: Thu, 28 Jul 2005 16:32:03 +0200 [thread overview]
Message-ID: <20050728143203.GJ3528@stusta.de> (raw)
In-Reply-To: <42E8E6BD.90807@gmail.com>
On Thu, Jul 28, 2005 at 04:07:57PM +0200, Jiri Slaby wrote:
> Adrian Bunk napsal(a):
>
> >On Thu, Jul 28, 2005 at 03:42:26PM +0200, Jiri Slaby wrote:
> >
> >
> >>Hi.
> >>Do you think, that this would be useful in the kernel tree?
> >>I have an idea to mark old drivers, which should I or somebody rewrite.
> >>For example drivers/isdn/hisax/gazel.c.
> >>...
> >>--- /dev/null
> >>+++ b/include/linux/oldapi.h
> >>@@ -0,0 +1,2 @@
> >>+#warning This driver uses old style API and needs to be rewritten or
> >>removed \
> >>+ from kernel
> >>
> >>
> >
> >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.
Why do you require a header file for this?
Simply put the #warning in gazel.c .
If the API is scheduled for removal, you should put the #warning in the
header file for the API.
If the API is old but is expected to stay for a longer time, simply do
nothing. Artificially increasing the warnings during kernel compilation
only makes it harder to find important warnings.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2005-07-28 14:32 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
2005-07-28 14:32 ` Adrian Bunk [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=20050728143203.GJ3528@stusta.de \
--to=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