From: Matthew Dobson <colpatch@us.ibm.com>
To: Martin Waitz <tali@admingilde.org>
Cc: Patrick Mochel <mochel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: cpu_devclass removed from cpu.h
Date: Mon, 04 Nov 2002 11:31:13 -0800 [thread overview]
Message-ID: <3DC6CB01.7080102@us.ibm.com> (raw)
In-Reply-To: 20021102003027.GD16236@admingilde.org
Martin Waitz wrote:
> hi :)
>
> the 'extern struct device_class cpu_devclass;' was removed from cpu.h
> lately.
> is this intentional or will it come back in some other include file?
>
> i need that class to be able to register a interface for cpus
> in my tree.
>
>
> thanks
There were no immediate plans to put that back in linux/cpu.h. It is
now defined and used in drivers/base/cpu.c. cpu_devclass is registered
with driverfs (err.. sysfs) there. If you need it, you should be able
to reference it... just stick an extern in your file.
Check out the thread '[patch] Core sysfs Topology 2.5.45'. These are
the patches that modified the sysfs topology system.
Cheers!
-Matt
next prev parent reply other threads:[~2002-11-04 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 0:30 cpu_devclass removed from cpu.h Martin Waitz
2002-11-04 19:31 ` Matthew Dobson [this message]
2002-11-05 22:09 ` Martin Waitz
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=3DC6CB01.7080102@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=tali@admingilde.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