From: Leandro Lucarella <luca@llucax.com.ar>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Kailang Yang <kailang@realtek.com>,
Daniel T Chen <crimsun@ubuntu.com>,
alsa-devel@alsa-project.org
Subject: Re: Regression 2.6.35: Intel N10/ICH 7 Family HDA (Realtek ALC662 rev1) beep broken
Date: Tue, 3 Aug 2010 13:00:13 -0300 [thread overview]
Message-ID: <20100803160013.GF3508@llucax.com.ar> (raw)
In-Reply-To: <s5h7hk7lnxg.wl%tiwai@suse.de>
Takashi Iwai, el 3 de agosto a las 17:24 me escribiste:
> > > I can add such a trivial patch manually, of course. But I'd need
> > > to know which machine you have (vendor/model name, etc).
> >
> > Is a desktop box.
> > CPU Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
> > Motherboard Intel Corporation DG41RQ
>
> OK, it's fine, I just wanted to be sure that it's no other brand.
> The fix is now applied to sound tree, and will be included in the next
> pull request, then will reach to stable tree.
Thank you.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
La esperanza es una amiga que nos presta la ilusión.
prev parent reply other threads:[~2010-08-03 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 4:00 Regression 2.6.35: Intel N10/ICH 7 Family HDA (Realtek ALC662 rev1) beep broken Leandro Lucarella
2010-08-03 5:42 ` Takashi Iwai
2010-08-03 5:42 ` Takashi Iwai
2010-08-03 13:44 ` Leandro Lucarella
2010-08-03 13:48 ` Takashi Iwai
2010-08-03 13:48 ` Takashi Iwai
2010-08-03 14:48 ` Leandro Lucarella
2010-08-03 15:24 ` Takashi Iwai
2010-08-03 15:24 ` Takashi Iwai
2010-08-03 16:00 ` Leandro Lucarella [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=20100803160013.GF3508@llucax.com.ar \
--to=luca@llucax.com.ar \
--cc=alsa-devel@alsa-project.org \
--cc=crimsun@ubuntu.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 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.