From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: [PATCH] 0/5 powerpc: Platform & i2c updates & cpufreq
Date: Sun, 08 Jan 2006 09:04:53 +1100 [thread overview]
Message-ID: <1136671493.30123.2.camel@localhost.localdomain> (raw)
In-Reply-To: <jemzi8umx2.fsf@sykes.suse.de>
On Sat, 2006-01-07 at 15:34 +0100, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>
> > This serie of patch replaces the 2 I posted recently for platform
> > functions & g5 cpufreq. It's not a 100% finished job yet but it's
> > getting closer.
>
> The patch appears to break ALSA on PowerMac Dual 1.8GHz. The volume
> control is going wild, and I'm getting distorted sound.
Which patch specifically ? I suspect a problem with the keywest i2c
code, I 'll have a look today or tomorrow.
Ben.
next prev parent reply other threads:[~2006-01-07 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 0:24 [PATCH] 0/5 powerpc: Platform & i2c updates & cpufreq Benjamin Herrenschmidt
2006-01-07 14:34 ` Andreas Schwab
2006-01-07 22:04 ` Benjamin Herrenschmidt [this message]
2006-01-07 22:09 ` Benjamin Herrenschmidt
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=1136671493.30123.2.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=schwab@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;
as well as URLs for NNTP newsgroup(s).