public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
	sdhci-devel@list.drzeus.cx, linux-kernel@vger.kernel.org
Subject: Re: [Sdhci-devel] PATCH: Fix 32bitism in SDHCI
Date: Thu, 15 Jun 2006 19:52:39 +0100	[thread overview]
Message-ID: <20060615185239.GC8694@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1150393058.3490.120.camel@localhost.localdomain>

On Thu, Jun 15, 2006 at 06:37:37PM +0100, Alan Cox wrote:
> Ar Iau, 2006-06-15 am 18:59 +0200, ysgrifennodd Pierre Ossman:
> > Alan Cox wrote:
> > > The data field is ulong, pointers fit in ulongs. Casting them to int is
> > > bad for 64bit systems.
> > 
> > It's in my (rather large) queue. I'm just waiting for a merge window. :)
> 
> I'd have thought that one was a "Duh whoops, fix it now" kind of
> submission for 2.6.17

akpm sent it to me, so I merged it into my tree, and now I've been
sitting on it all this week because I've taken the decision that I
do not want to put anything further into Linus' tree until we actually
see 2.6.17.

If you look at what Linus said when he released -rc7, the reason we
had -rc7 instead of -final was that we had too many changes.  We can
either go on throwing more and more changes, albiet 100% correct
bug fix changes, and carry on releasing -rc after -rc, but at some
point there must be an end to this, and -final must happen.

It's been three months since 2.6.16 was released.  I'm not prepared
to be the reason that we have another week of -rc-ism because of too
many small but apparantly correct changes.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  parent reply	other threads:[~2006-06-15 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 15:33 PATCH: Fix 32bitism in SDHCI Alan Cox
2006-06-15 16:59 ` [Sdhci-devel] " Pierre Ossman
2006-06-15 17:04   ` Russell King
2006-06-15 17:07     ` Pierre Ossman
2006-06-15 17:37   ` Alan Cox
2006-06-15 18:35     ` Mark Lord
2006-06-15 18:50     ` Pierre Ossman
2006-06-15 21:51       ` Alan Cox
2006-06-15 18:52     ` Russell King [this message]
2006-06-15 18:59   ` Daniel Drake
2006-06-15 19:05     ` Pierre Ossman

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=20060615185239.GC8694@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdhci-devel@list.drzeus.cx \
    /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