From: Rusty Russell <rusty@rustcorp.com.au>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Anton Blanchard <anton@samba.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH][0/6] CPU Hotplug update + fixes
Date: Tue, 04 Feb 2003 16:49:15 +1100 [thread overview]
Message-ID: <20030204065845.1D5612C157@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 03 Feb 2003 06:34:21 CDT." <Pine.LNX.4.44.0302030301120.9361-100000@montezuma.mastecende.com>
In message <Pine.LNX.4.44.0302030301120.9361-100000@montezuma.mastecende.com> y
ou write:
> Hi,
> These patches are in no way an attempt to push this for inclusion,
> but instead a bit of grunt work to keep it current. However i would
> very much so like see it included in mainline.
Zwane, please send me your physical address so I can put you on my Christmas
list 8)
I've stolen these, removed a couple of unrelated cleanups to shrink
it, and put them on my page with you as author (and me as coauthor).
Here are the parts I pulled out (BTW, I'm missing 4/6: can you
re-xmit?)
Index: linux-2.5.59-lch2/include/linux/cpu.h
===================================================================
RCS file: /build/cvsroot/linux-2.5.59/include/linux/cpu.h,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- linux-2.5.59-lch2/include/linux/cpu.h 17 Jan 2003 11:15:50 -0000 1.1.1.1
+++ linux-2.5.59-lch2/include/linux/cpu.h 20 Jan 2003 13:48:27 -0000 1.1.1.1.2.1
@@ -1,3 +1,5 @@
+#ifndef _LINUX_CPU_H
+#define _LINUX_CPU_H
/*
* include/linux/cpu.h - generic cpu definition
*
@@ -16,8 +18,6 @@
* - drivers/base/intf.c
* - Documentation/driver-model/interface.txt
*/
-#ifndef _LINUX_CPU_H_
-#define _LINUX_CPU_H_
#include <linux/device.h>
#include <linux/node.h>
Index: linux-2.5.59-lch2/drivers/base/cpu.c
===================================================================
RCS file: /build/cvsroot/linux-2.5.59/drivers/base/cpu.c,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- linux-2.5.59-lch2/drivers/base/cpu.c 17 Jan 2003 11:15:18 -0000 1.1.1.1
+++ linux-2.5.59-lch2/drivers/base/cpu.c 20 Jan 2003 13:48:26 -0000 1.1.1.1.2.1
@@ -14,11 +14,11 @@
{
return 0;
}
+
struct device_class cpu_devclass = {
.name = "cpu",
.add_device = cpu_add_device,
};
-
struct device_driver cpu_driver = {
.name = "cpu",
Index: linux-2.5.59-lch2/mm/page-writeback.c
===================================================================
RCS file: /build/cvsroot/linux-2.5.59/mm/page-writeback.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 page-writeback.c
--- linux-2.5.59-lch2/mm/page-writeback.c 17 Jan 2003 11:16:41 -0000 1.1.1.1
+++ linux-2.5.59-lch2/mm/page-writeback.c 21 Jan 2003 04:48:29 -0000
@@ -350,6 +350,7 @@
static int
ratelimit_handler(struct notifier_block *self, unsigned long u, void *v)
{
+ /* This should be fine for all cases */
set_ratelimit();
return 0;
}
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-02-04 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 11:34 Zwane Mwaikambo
2003-02-03 12:08 ` Zwane Mwaikambo
2003-02-04 5:49 ` Rusty Russell [this message]
2003-02-05 2:47 ` Zwane Mwaikambo
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=20030204065845.1D5612C157@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@digeo.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zwane@holomorphy.com \
/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®