public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org, pj@sgi.com
Subject: Re: 2.6.6-rc1-mm1
Date: Mon, 19 Apr 2004 00:06:43 -0700	[thread overview]
Message-ID: <20040419070643.GG743@holomorphy.com> (raw)
In-Reply-To: <20040419064943.GF743@holomorphy.com>

On Sun, Apr 18, 2004 at 11:49:43PM -0700, William Lee Irwin III wrote:
> Quick story is that what I sent is (what I believe) to be the bare
> minimum change to restore correctnes.
> I'll start arguing with people to make sure bugfixes start moving and
> cleanups start waiting.
> Paul, please remove akpm from the cc: list in future replies until we
> have come to a consensus and get this nailed down (hopefully ASAP) to
> a coherent cross-vendor story.
> What I believe I have sent is the bare minimum change, with no cleanups
> or semantic changes. If you could review and/or send approval or the
> like that would be very helpful for the users of small SMP systems who
> are affected by the bug(s) you reported.

One last thing: I'm not opposed to cleanups in the least.

What I'm most concerned about is that arch maintainers have their needs
satisfied by whatever internals you choose to back cpumask* with.

In all honesty, what you've been proposing is very close to what I wanted
to have done to begin with. I would be glad to have you (or whoever else
has the wherewithal to push the issue) get things down to the cleanest and
most generally applicable implementation of API or definition of API as
possible.

I have taken issue only where I believe you need to acquire arch maintainer
feedback. IMHO, the changes proposed would be cleanups and more extensible,
but only need the review from arch maintainers to bring them to full
mainline merging. This is an API. When you have semantic equivalence, as
approved by arch maintainers, this has no reason _not_ to go in.

All this said, you have pointed out immediate needs for fixes. Please let
these fixes go through. There is a difference between the best code
possible and what makes things work.


-- wli

  reply	other threads:[~2004-04-19  7:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  6:01 2.6.6-rc1-mm1 Andrew Morton
2004-04-19  6:29 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19  6:42   ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-19  6:49     ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19  7:06       ` William Lee Irwin III [this message]
2004-04-19 18:39         ` bitmap, cpumask_arith (was: 2.6.6-rc1-mm1) Paul Jackson
2004-04-20 21:17           ` Paul Jackson
2004-04-20 21:38             ` William Lee Irwin III
2004-04-19  6:58   ` 2.6.6-rc1-mm1 Nick Piggin
2004-04-19  9:13 ` 2.6.6-rc1-mm1 failure: kmod.o didn't compile with module-less setup Helge Hafting
2004-04-19  9:17   ` Andrew Morton
2004-04-19 15:26 ` 2.6.6-rc1-mm1 (compile stats) John Cherry
2004-04-19 19:25 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-20  1:13   ` 2.6.6-rc1-mm1 Ian Kent
2004-04-20  1:26     ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-21  9:08       ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:31         ` 2.6.6-rc1-mm1 raven
2004-04-21 13:18           ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:34             ` 2.6.6-rc1-mm1 raven
2004-04-21 15:52             ` 2.6.6-rc1-mm1 raven
2004-04-21 16:09               ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:39         ` 2.6.6-rc1-mm1 raven
2004-04-21 13:19           ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:52             ` 2.6.6-rc1-mm1 raven
2004-04-21 14:56               ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 15:39                 ` 2.6.6-rc1-mm1 raven
2004-04-20 14:27 ` 2.6.6-rc1-mm1 raven
2004-04-20 15:06 ` 2.6.6-rc1-mm1 Rik van Riel
2004-04-21  7:37   ` 2.6.6-rc1-mm1 Sean Neakums
2004-04-21 12:16     ` 2.6.6-rc1-mm1 Hugh Dickins

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=20040419070643.GG743@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --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