All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Francisco Moraes <fmoraes@nc.rr.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Bug report 752
Date: Thu, 17 Mar 2005 13:39:58 +0100	[thread overview]
Message-ID: <s5hvf7q78f5.wl@alsa2.suse.de> (raw)
In-Reply-To: <42397859.6020102@nc.rr.com>

At Thu, 17 Mar 2005 07:30:17 -0500,
Francisco Moraes wrote:
> 
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=752
> 
> Anyone got ideas on this?

Most likely a false positive.  Since "EMU10K1X: ..." message did
appear in the earlier version (as mentioned in the original report),
the printk must appear.

I guess he modified a wrong source tree and installed the module in a
wrong path.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-03-17 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 12:30 Bug report 752 Francisco Moraes
2005-03-17 12:39 ` Takashi Iwai [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=s5hvf7q78f5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=fmoraes@nc.rr.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.