public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "David S. Miller" <davem@redhat.com>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask_t
Date: Sun, 19 Jan 2003 22:32:19 -0800	[thread overview]
Message-ID: <20030120063219.GL780@holomorphy.com> (raw)
In-Reply-To: <20030119.221013.65242960.davem@redhat.com>

On Sun, Jan 19, 2003 at 10:10:13PM -0800, David S. Miller wrote:
> I'm totally fine with this work, in fact I consider it
> a cleanup.
> I could call it a bug fix, but that would be stretching it :-)

I'll try to maintain it, then. It's received zero runtime testing,
esp. not in true NR_CPUS > BITS_PER_LONG circumstances. But I don't
have any kind of regular (read as: once annually or less) access to
such systems, so the best I can do is chip in and attempt to keep
(largely untested/untestable) patches current.

This looks like it diverged a little bit from rusty's implementation,
partly because I thought it'd be easier to just pound things out from
scratch as opposed to attempting to port directly.

rusty, if you could comment on the differences, I'd be much obliged.

I'll also attempt to get a SPARC toolchain together (as I understand it,
there are some divergences from mainline/current gcc/binutils) and do
some compiletesting-like and API conversion things there.

Thanks,
Bill

  reply	other threads:[~2003-01-20  6:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  7:39 [PATCH] cpumask_t Rusty Russell
2002-08-08 14:36 ` David S. Miller
2002-08-09  6:04   ` Rusty Russell
2002-08-09 10:10     ` Brad Heilbrun
2003-01-19 21:35     ` William Lee Irwin III
2003-01-19 22:18       ` William Lee Irwin III
2003-01-19 22:43         ` William Lee Irwin III
2003-01-19 22:54           ` William Lee Irwin III
2003-02-10  7:06             ` William Lee Irwin III
2003-01-20  6:10       ` David S. Miller
2003-01-20  6:32         ` William Lee Irwin III [this message]
2003-01-20  6:24           ` David S. Miller

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=20030120063219.GL780@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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