From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: "Ishan Jayawardena" <ioshadij@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)
Date: Mon, 18 Feb 2002 11:25:05 -0700 [thread overview]
Message-ID: <200202181825.g1IIP5D01884@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <F74iP3FJVRA4kB7CA5r0001cc7d@hotmail.com>
In-Reply-To: <F74iP3FJVRA4kB7CA5r0001cc7d@hotmail.com>
Ishan Jayawardena writes:
> This is a multi-part message in MIME format.
First comment: please send the patch inline, not MIME-encoded.
> I'd love to extend this work to support Paul Russell's hotplug cpu work, but
> I have absolutely no way at present to test it. (If some kind party would
> like to donate a quad pentium 4 Xeon with hotplug cpu support, I'll be more
> than happy to do so ;)
>
> This is against 2.4.18-pre9-ac4 with devfs v199.9
>
> Relevent comments, advise, improvisations, flames, welcome.
Second comment: devfs_(un)register_per_cpu() doesn't belong in
fs/devfs/base.c. I don't even think it should be in fs/devfs/util.c.
I think it belongs kernel/smp.c (that's right, create a new file).
There's too much duplicated SMP code in each arch/ tree. Let's create
a place for new stuff to be shared.
So, please send along your next version of the patch (inlined, of
course:-).
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-02-18 18:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 10:50 Ishan Jayawardena
2002-02-18 18:25 ` Richard Gooch [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 11:13 Matt Dainty
2002-01-06 18:17 ` Matt Dainty
2002-01-06 19:34 ` Richard Gooch
2002-01-06 20:43 ` Matt Dainty
2002-01-06 21:08 ` H. Peter Anvin
2002-01-06 21:11 ` Richard Gooch
2002-01-06 21:12 ` H. Peter Anvin
2002-01-06 21:06 ` H. Peter Anvin
2002-01-06 21:08 ` Richard Gooch
2002-01-06 21:10 ` H. Peter Anvin
2002-01-06 21:36 ` Russell King
2002-01-07 0:44 ` H. Peter Anvin
2002-01-07 1:31 ` Richard Gooch
2002-01-07 1:32 ` H. Peter Anvin
2002-01-07 1:40 ` Richard Gooch
2002-01-07 1:44 ` H. Peter Anvin
2002-01-08 9:14 ` Rusty Russell
2002-01-08 12:02 ` Matt Dainty
2002-01-08 17:17 ` H. Peter Anvin
2002-01-08 17:35 ` Richard Gooch
2002-01-09 1:01 ` Rusty Russell
2002-01-09 3:16 ` H. Peter Anvin
2002-01-09 3:28 ` Rusty Russell
2002-01-09 3:30 ` Richard Gooch
2002-01-09 3:47 ` H. Peter Anvin
2002-01-09 5:41 ` Richard Gooch
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=200202181825.g1IIP5D01884@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=ioshadij@hotmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®