From: Miles Bader <miles@lsi.nec.co.jp>
To: Andrew Morton <akpm@digeo.com>
Cc: zwane@linuxpower.ca, linux-kernel@vger.kernel.org
Subject: Re: Oops: 2.5.64 check_obj_poison for 'size-64'
Date: 07 Mar 2003 17:10:23 +0900 [thread overview]
Message-ID: <buobs0n1tsg.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20030306235845.661fc4ab.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> writes:
> Although at some point we really do need to stop cleaning stuff up,
> defer such things into 2.7 and concentrate upon 2.5 bugs.
Agreed, though I think this particular cleanup is almost absurdly
straight-forward, and seems very unlikely to cause any problems
(for the most part it's really just moving stuff from one file to
another).
I'd think all the spelling corrections would be more controversial. :-)
-Miles
--
Suburbia: where they tear out the trees and then name streets after them.
next prev parent reply other threads:[~2003-03-07 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 5:13 Zwane Mwaikambo
2003-03-07 6:23 ` Andrew Morton
2003-03-07 7:22 ` Zwane Mwaikambo
2003-03-07 7:35 ` Andrew Morton
2003-03-07 7:40 ` Zwane Mwaikambo
2003-03-07 7:45 ` Miles Bader
2003-03-07 7:58 ` Andrew Morton
2003-03-07 8:10 ` Miles Bader [this message]
2003-03-07 10:05 ` [PATCH] protect 'action' in show_interrupts Zwane Mwaikambo
2003-03-07 10:28 ` Andrew Morton
2003-03-07 15:32 ` Zwane Mwaikambo
2003-03-07 15:46 ` Russell King
2003-03-07 16:25 ` Zwane Mwaikambo
2003-03-07 22:01 ` Andrew Morton
[not found] ` <Pine.LNX.4.50.0303070351060.18716-100000@montezuma.mastecende.com>
[not found] ` <20030307010539.3c0a14a3.akpm@digeo.com>
2003-03-07 9:53 ` Oops: 2.5.64 check_obj_poison for 'size-64' Zwane Mwaikambo
2003-03-07 19:38 ` Manfred Spraul
2003-03-07 21:57 ` Zwane Mwaikambo
2003-03-08 2:11 ` Zwane Mwaikambo
2003-03-08 2:24 ` Andrew Morton
2003-03-08 2:42 ` 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=buobs0n1tsg.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=zwane@linuxpower.ca \
/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®