From: Takashi Iwai <tiwai@suse.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headers_check: special case seqbuf_dump()
Date: Thu, 16 Jan 2014 12:53:00 +0100 [thread overview]
Message-ID: <s5h4n54ta77.wl%tiwai@suse.de> (raw)
In-Reply-To: <1389782899.2128.15.camel@x220>
At Wed, 15 Jan 2014 11:48:19 +0100,
Paul Bolle wrote:
>
> "make headers_check" warns about soundcard.h for (at least) five years
> now:
> [...]/usr/include/linux/soundcard.h:1054: userspace cannot reference function or variable defined in the kernel
>
> We're apparently stuck with providing OSSlib-3.8 compatibility, so let's
> special case this declaration just to silence it.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> 0) Support for OSSlib post 3.8 was already removed in commit 43a990765a
> ("sound: Remove OSSlib stuff from linux/soundcard.h"). Five years have
> passed since that commit: do people still care about OSSlib-3.8? If not,
> quite a bit of code could be remove from soundcard.h (and probably
> ultrasound.h).
Such a thing is always hard to know, just like to find a Bigfoot :)
> 2) By the way, what is actually meant by:
> It is no longer possible to actually link against OSSlib with this
> header, but we still provide these macros for programs using them.
>
> Doesn't that mean compatibility to OSSlib isn't even useful?
Well, it's not about the compatibility to osslib. The OSS seq
user-space codes are written with these macros no matter whether to
use osslib or not. osslib was newer than these macros and it was
designed to be compatible with them.
thanks,
Takashi
> 3) Anyhow, a previous discussion soundcard.h, which led to that commit,
> starts at https://lkml.org/lkml/2009/1/20/349 .
>
> 4) And, yes, I sneaked in a whitespace fix.
>
> scripts/headers_check.pl | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/headers_check.pl b/scripts/headers_check.pl
> index 64ac238..62320f9 100644
> --- a/scripts/headers_check.pl
> +++ b/scripts/headers_check.pl
> @@ -65,7 +65,11 @@ sub check_include
>
> sub check_declarations
> {
> - if ($line =~m/^(\s*extern|unsigned|char|short|int|long|void)\b/) {
> + # soundcard.h is what it is
> + if ($line =~ m/^void seqbuf_dump\(void\);/) {
> + return;
> + }
> + if ($line =~ m/^(\s*extern|unsigned|char|short|int|long|void)\b/) {
> printf STDERR "$filename:$lineno: " .
> "userspace cannot reference function or " .
> "variable defined in the kernel\n";
> --
> 1.8.4.2
>
next prev parent reply other threads:[~2014-01-16 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 10:48 Paul Bolle
2014-01-15 13:28 ` Arnd Bergmann
2014-01-16 11:53 ` Takashi Iwai [this message]
2014-01-16 12:39 ` Paul Bolle
2014-01-16 13:51 ` Takashi Iwai
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=s5h4n54ta77.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
/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
all inboxes | Powered by JetHome®