public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.11 breaks snd_printk if SND_VERBOSE_PRINTK = n
Date: Tue, 30 Apr 2002 00:20:57 +0200	[thread overview]
Message-ID: <3CCDC749.9070505@oracle.com> (raw)

with CONFIG_SND_VERBOSE_PRINTK = n :

make[4]: Entering directory `/usr/local/src/linux-2.5.11/sound/core/seq/oss'
gcc -D__KERNEL__ -I/usr/local/src/linux-2.5.11/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE  -DKBUILD_BASENAME=seq_oss  -c -o seq_oss.o seq_oss.c
seq_oss.c:225:17: warning: pasting "(" and "KERN_ERR" does not give a valid preprocessing token
seq_oss.c: In function `register_device':
seq_oss.c:225: `KERN_ERR' undeclared (first use in this function)
seq_oss.c:225: (Each undeclared identifier is reported only once
seq_oss.c:225: for each function it appears in.)
seq_oss.c:225: parse error before string constant
seq_oss.c:233:17: warning: pasting "(" and "KERN_ERR" does not give a valid preprocessing token
seq_oss.c:233: parse error before string constant
seq_oss.c:238:9: warning: pasting "(" and ""device registered\n"" does not give a valid preprocessing token
seq_oss.c:247:9: warning: pasting "(" and ""device unregistered\n"" does not give a valid preprocessing token
seq_oss.c:249:17: warning: pasting "(" and "KERN_ERR" does not give a valid preprocessing token

etc. etc.

Configuring SND_VERBOSE_PRINTK in makes the problem go away.

--alessandro

  "the hands that build / can also pull down
    even the hands of love"
                             (U2, "Exit")


                 reply	other threads:[~2002-04-29 22:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CCDC749.9070505@oracle.com \
    --to=alessandro.suardi@oracle.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