From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: sysfs cpu entry
Date: Sun, 27 Apr 2008 09:10:30 +1000 [thread overview]
Message-ID: <1209251430.5420.44.camel@pasglop> (raw)
In-Reply-To: <4811593B.8080508@hypersurf.com>
On Thu, 2008-04-24 at 21:08 -0700, Kevin Diggs wrote:
> P.S.: On an unrelated note, anyone know where to start looking for
> problems in pmac_zilog. My 8600 modem which worked fine in 2.4 is now
> essentially useless. Some problem with handshaking, I think.
It's possible that handshaking is broken, I remember some nasty tricks
with it on some Apple HW and I may have gotten that wrong...
Ben.
next prev parent reply other threads:[~2008-04-26 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 4:08 sysfs cpu entry Kevin Diggs
2008-04-25 3:36 ` Kumar Gala
2008-04-26 7:16 ` Kevin Diggs
2008-04-26 23:10 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 22:05 Kevin Diggs
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=1209251430.5420.44.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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 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).