public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>,
	"Friedrich Göpel" <shado23@gmail.com>,
	"LKML Kernel" <linux-kernel@vger.kernel.org>,
	alsa-user@lists.sourceforge.net, "Takashi Iwai" <tiwai@suse.de>
Subject: Re: hda-intel woes
Date: Mon, 27 Mar 2006 20:28:45 -0500	[thread overview]
Message-ID: <1143509326.1792.339.camel@mindpipe> (raw)
In-Reply-To: <69495D2A-5488-428E-970F-EA4DD8CB4C05@mac.com>

On Mon, 2006-03-27 at 20:22 -0500, Kyle Moffett wrote:
> Friedrich Göpel wrote:
> > This same message was sent to the alsa mailinglist 3 weeks ago, but  
> > it still seems to be waiting on being moderated, so I'm resending  
> > this here.
> 
> Hi!  Unfortunately messages tend to get lost on occasion due to the  
> sheer volume of email.  Sometimes you may have to resend a couple  
> times to get a response.  It also helps if you add relevant CC's from  
> the MAINTAINERS file (added to this message).  You can also file a  
> bug report on the ALSA bug tracker, I think the ALSA people tend to  
> be fairly good about keeping up with that; sometimes more so than the  
> mailing list.

First, try ALSA CVS - many hda-intel bugs have been fixed since
1.0.11-rc3.

Lee


  reply	other threads:[~2006-03-28  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 23:10 hda-intel woes Friedrich Göpel
2006-03-28  0:45 ` Jeff V. Merkey
2006-03-28  0:22   ` Friedrich Göpel
2006-03-28  1:22   ` Kyle Moffett
2006-03-28  1:28     ` Lee Revell [this message]
2006-03-28 16:57     ` Friedrich Göpel
2006-03-28 23:10   ` Bill Davidsen
2006-03-29  0:21     ` Jeff V. Merkey
2006-03-29 17:14       ` Bill Davidsen
2006-03-29 18:18         ` Jeff V. Merkey
2006-03-28  8:29 ` Petri Kaukasoina

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=1143509326.1792.339.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=shado23@gmail.com \
    --cc=tiwai@suse.de \
    /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