Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: pci_disable_device warning
Date: Wed, 17 Nov 2004 13:40:48 -0500	[thread overview]
Message-ID: <1100716849.6930.31.camel@krustophenia.net> (raw)

I get this warning when removing ALSA modules.  I believe the warning is
going away, so maybe we should address the issue now.  Is this something
that could be done by the ALSA middle layer? 

Nov 16 23:32:09 krustophenia kernel: EMU10K1_Audigy 0000:00:14.0: Device
was removed without properly calling pci_disable_device(). This may need
fixing.

I tried adding a call to pci_disable_device and the warning persisted,
maybe I did not add it in the right place.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

             reply	other threads:[~2004-11-17 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 18:40 Lee Revell [this message]
2004-11-18 13:08 ` pci_disable_device warning 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=1100716849.6930.31.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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