From: Kevin Diggs <kevdig@hypersurf.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: sysfs cpu entry
Date: Sat, 26 Apr 2008 00:16:10 -0700 [thread overview]
Message-ID: <4812D6BA.6060003@hypersurf.com> (raw)
In-Reply-To: <8564AA3F-C745-4A5A-952F-477B6A68681C@kernel.crashing.org>
Kumar Gala wrote:
>
> What 32-bit chip are you looking to enable this for?
>
> - k
>
I am working on some stuff for the 750GX
kevin
next prev parent reply other threads:[~2008-04-26 6:28 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 [this message]
2008-04-26 23:10 ` Benjamin Herrenschmidt
-- 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=4812D6BA.6060003@hypersurf.com \
--to=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 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.