From: Rusty Russell <rusty@rustcorp.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
ak@suse.de, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] fix sys cpumap for > 352 NR_CPUS
Date: Thu, 03 Jun 2004 14:35:04 +1000 [thread overview]
Message-ID: <1086237304.29391.406.camel@bach> (raw)
In-Reply-To: <20040602213432.05f48058.pj@sgi.com>
On Thu, 2004-06-03 at 14:34, Paul Jackson wrote:
> Rusty wrote:
> > Above all, by placing your questions inside a patch, you got results,
> > but please don't do this again.
>
> Ah yes ...
>
> Apparently, Rusty, you are unfamiliar with the style of coding that
> involves "put in an ugly hack now, commenting the known open issues,
> and then clean up the mess some other day".
Known open issues I have no problems with. It's asking questions in the
comments that I disagree with: either you should ask on lkml, or grep.
To be honest, if you can't figure out the answers, you have to ask if
you're the right person to be modifying the code.
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-06-03 4:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:11 [PATCH] fix sys cpumap for > 352 NR_CPUS Paul Jackson
2004-06-02 23:23 ` Andrew Morton
2004-06-02 23:59 ` Paul Jackson
2004-06-03 0:17 ` Andrew Morton
2004-06-03 16:24 ` Greg KH
2004-06-03 16:28 ` Paul Jackson
2004-06-03 0:22 ` Rusty Russell
2004-06-03 4:25 ` Paul Jackson
2004-06-03 6:26 ` Rusty Russell
2004-06-03 8:27 ` Paul Jackson
2004-06-04 1:12 ` Rusty Russell
2004-06-04 2:25 ` Paul Jackson
2004-06-03 15:49 ` Paul Jackson
2004-06-03 4:34 ` Paul Jackson
2004-06-03 4:35 ` Rusty Russell [this message]
2004-06-03 16:27 ` Greg KH
2004-06-03 16:38 ` Paul Jackson
2004-06-03 16:51 ` Greg KH
2004-06-04 1:27 ` Rusty Russell
2004-06-04 18:15 ` Greg KH
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=1086237304.29391.406.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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