From: Lee Revell <rlrevell@joe-job.com>
To: "Yang, Libin" <libin.yang@intel.com>
Cc: bugtrack@alsa-project.org, alsa-devel@alsa-project.org
Subject: RE: [ALSA - driver 0001563]: No Sound on Cybersystem S28 (hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...)
Date: Tue, 22 Nov 2005 21:49:22 -0500 [thread overview]
Message-ID: <1132714162.4774.9.camel@mindpipe> (raw)
In-Reply-To: <D4DBC33C8102AB409C7F44B414D9943801593CE2@bjsmsx402.ccr.corp.intel.com>
On Wed, 2005-11-23 at 10:45 +0800, Yang, Libin wrote:
> I think I have found the reason which may cause the problem. But I don't how to submit the patch or just write the reason here? Thanks.
Thanks very much for fixing this.
You can just post the patch here, with the description and Signed-Off-By
line.
Lee
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
next prev parent reply other threads:[~2005-11-23 2:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 2:45 [ALSA - driver 0001563]: No Sound on Cybersystem S28 (hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...) Yang, Libin
2005-11-23 2:49 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-24 12:18 bugtrack
2005-11-24 7:48 bugtrack
2005-11-23 19:31 bugtrack
2005-11-23 19:08 bugtrack
2005-11-23 15:25 bugtrack
2005-11-22 18:32 bugtrack
2005-11-22 18:15 bugtrack
2005-11-22 18:08 bugtrack
2005-11-22 17:36 bugtrack
2005-11-18 18:49 bugtrack
2005-11-18 16:00 bugtrack
2005-11-18 5:49 bugtrack
2005-11-16 5:48 bugtrack
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=1132714162.4774.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@alsa-project.org \
--cc=bugtrack@alsa-project.org \
--cc=libin.yang@intel.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.