From: Russell King <rmk@arm.linux.org.uk>
To: Keith Owens <kaos@ocs.com.au>
Cc: Tom Rini <trini@kernel.crashing.org>,
kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [kbuild-devel] (no subject)
Date: Fri, 7 Dec 2001 11:01:58 +0000 [thread overview]
Message-ID: <20011207110158.B1500@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20011207043059.GI30935@cpe-24-221-152-185.az.sprintbbd.net> <24800.1007699773@kao2.melbourne.sgi.com>
In-Reply-To: <24800.1007699773@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Fri, Dec 07, 2001 at 03:36:13PM +1100
On Fri, Dec 07, 2001 at 03:36:13PM +1100, Keith Owens wrote:
> We will not get all architectures converted in 48 hours or even 72.
> kbuild 2.5 has been available for months and only i386, ia64, sparc32
> (I did all those) and sparc64 (Ben Collins) have been converted. Alpha
> is in progress. Unconverted architectures stay on 2.5.2-pre1 until
> they do the conversion, but there is no need to hold up everybody else.
It's a shame that you were too busy to discuss the bugs I found in
kbuild 2.5 6 months ago when I tried it on ARM, despite me following
it up since.
My sympathies are with Tom here, and I think there should be longer than
24 hours for this.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-12-07 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 4:17 Keith Owens
2001-12-07 4:30 ` [kbuild-devel] (no subject) Tom Rini
2001-12-07 4:36 ` Keith Owens
2001-12-07 4:41 ` Tom Rini
2001-12-07 11:01 ` Russell King [this message]
2001-12-07 11:07 ` Keith Owens
2001-12-07 5:10 ` your mail Linus Torvalds
2001-12-07 5:12 ` [kbuild-devel] " Eric S. Raymond
2001-12-07 8:29 ` Converting the 2.5 kernel to kbuild 2.5 Keith Owens
2001-12-27 18:09 ` your mail Andre Hedrick
2001-12-27 18:55 ` Linus Torvalds
2001-12-27 19:41 ` Andrew Morton
2001-12-28 22:14 ` Martin Dalecki
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=20011207110158.B1500@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trini@kernel.crashing.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.