From: Bdale Garbee <bdale@gag.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with codec discovery on HP 2530p
Date: Wed, 11 Nov 2009 16:48:03 -0500 [thread overview]
Message-ID: <1257976083.5237.1.camel@rover> (raw)
In-Reply-To: <s5hy6md600u.wl%tiwai@suse.de>
On Wed, 2009-11-11 at 07:36 +0100, Takashi Iwai wrote:
> But, single_cmd=1 is obviously not good. This options is just for
> debugging purpose. That's why that commit hits.
Ok, thanks, that fixed it.
I wasn't aware that I'd done something to set that option, but indeed I
had. Perhaps it fixed a problem in some earlier kernel revision... I
really do not recall!
Bdale
next prev parent reply other threads:[~2009-11-11 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 14:53 problem with codec discovery on HP 2530p Bdale Garbee
2009-11-10 16:43 ` Takashi Iwai
2009-11-10 20:56 ` Bdale Garbee
2009-11-11 6:36 ` Takashi Iwai
2009-11-11 21:48 ` Bdale Garbee [this message]
2009-11-12 6:47 ` Takashi Iwai
2009-11-12 19:26 ` Matthew Garrett
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=1257976083.5237.1.camel@rover \
--to=bdale@gag.com \
--cc=linux-kernel@vger.kernel.org \
--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