From: Piotr Hosowicz <piotr@hosowicz.com>
To: piotr@hosowicz.com
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
tj@kernel.org, linux-next@vger.kernel.org
Subject: Re: Intel sound proke in today;s next
Date: Fri, 23 Jul 2010 20:27:45 +0200 [thread overview]
Message-ID: <4C49DF21.5010109@example.com> (raw)
In-Reply-To: <4C49DE64.6000902@example.com>
On 23.07.2010 20:24, Piotr Hosowicz wrote:
> Hello,
>
> I just downloaded today's next and built it, then booted. Sound is not
> working, my card is:
>
> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
> Controller
>
> I am now booted with latest git kernel and cannot provide more info
> here
RC6, sorry
--
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- W którym mieście europejskim powstała pierwsza opera?
- Sydney.
NP: -
NB: 2.6.35-rc6
next prev parent reply other threads:[~2010-07-23 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 6:49 linux-next: Tree for July 23 Stephen Rothwell
2010-07-23 16:08 ` linux-next: Tree for July 23 (fscache) Randy Dunlap
2010-07-23 18:24 ` Intel sound proke in today;s next Piotr Hosowicz
2010-07-23 18:27 ` Piotr Hosowicz [this message]
2010-07-24 1:59 ` Stephen Rothwell
2010-07-25 15:27 ` Takashi Iwai
2010-07-25 15:56 ` Piotr Hosowicz
2010-07-26 7:29 ` Takashi Iwai
2010-07-26 16:57 ` Piotr Hosowicz
2010-07-26 17:24 ` Takashi Iwai
2010-07-26 17:33 ` Piotr Hosowicz
2010-07-26 18:00 ` Takashi Iwai
2010-07-26 18:30 ` Piotr Hosowicz
2010-07-26 19:03 ` Piotr Hosowicz
2010-07-26 20:17 ` Takashi Iwai
2010-07-26 20:54 ` Piotr Hosowicz
2010-07-27 5:41 ` Takashi Iwai
2010-07-24 9:14 ` [PATCH wq#for-next] fscache: fix build on !CONFIG_SYSCTL Tejun Heo
2010-07-25 22:18 ` Randy Dunlap
2010-07-23 16:41 ` [PATCH -next] compal-laptop: depends on POWER_SUPPLY Randy Dunlap
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=4C49DF21.5010109@example.com \
--to=piotr@hosowicz.com \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
/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.