public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Errors in OSS Sound Blaster driver / DMA Documentation (KERN_WARN)
Date: Fri, 3 Jul 2009 15:20:27 +0200	[thread overview]
Message-ID: <200907031520.27883.bzolnier@gmail.com> (raw)
In-Reply-To: <f4527be0907030454q290fe99t73161a0fd6c1d4d2@mail.gmail.com>

On Friday 03 July 2009 13:54:25 Andrew Lyon wrote:
> Hi,
> 
> While investigating a compile failure of Xen kernel I noticed that the
> OSS Sound Blaster driver and DMA Documentation have the same problem,
> KERN_WARNING Is valid and declared in include/linux/kernel.h,
> KERN_WARN does not exist, here are the affected files:
> 
> Documentation/DMA-mapping.txt:          printk(KERN_WARN "%s: Playback
> disabled due to DMA limitations.\n",
> Documentation/DMA-mapping.txt:          printk(KERN_WARN "%s: Record
> disabled due to DMA limitations.\n",
> arch/x86/kernel/cpu/common-xen.c:               printk(KERN_WARN
> "Unable to register CSTAR callback\n");
> sound/oss/sb_common.c:                          /* printk(KERN_WARN
> "Sound Blaster: Unexpected interrupt\n"); */
> sound/oss/sb_common.c:                          /* printk(KERN_WARN
> "Sound Blaster: Unexpected interrupt\n"); */
> sound/oss/sb_ess.c:                     /* printk(KERN_WARN "ESS:
> Unexpected interrupt\n"); */

Good spotting.  Care to send fixes for DMA-mapping / xen / sb?

Thanks.
Bart

      reply	other threads:[~2009-07-03 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 11:54 Errors in OSS Sound Blaster driver / DMA Documentation (KERN_WARN) Andrew Lyon
2009-07-03 13:20 ` Bartlomiej Zolnierkiewicz [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=200907031520.27883.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=andrew.lyon@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