From: Russell King <rmk@arm.linux.org.uk>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: Wed, 4 Dec 2002 12:35:17 +0000 [thread overview]
Message-ID: <20021204123517.A3563@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021204115819.GB1137@gallifrey>; from gilbertd@treblig.org on Wed, Dec 04, 2002 at 11:58:19AM +0000
On Wed, Dec 04, 2002 at 11:58:19AM +0000, Dr. David Alan Gilbert wrote:
> Don't forget that ia64, x86-64 and s390 are all potentially growing
> users of Linux. Linux on ARM, MIPS and PPC also has a healthy band of
> productive (commercial and home) users.
ARM Linux still has rather a large patch, but it is gradually getting
smaller again as things get merged.
As far as keeping the bits that are in Linus' kernel buildable (and
working), it is easier with the various BK cset patches or BK itself
because you can always be on top of Linus' tree. However, there are
costs here:
1. An incompatible change can be merged at any time into Linus' tree,
so frequent testing is required - might need a build system that
automatically builds Linus' kernels for an architecture nightly.
2. As a result of (1), even if it built at the last test, that's no
guarantee that the patch Linus releases will work - changes have
appeared around the time of the release which break architecture
code.
I would like to setup an automatic nightly ARM kernel build of the
current BK tree for multiple ARM machine types to get as much code
build-tested as possible.
However, this currently isn't feasible for me since most of the machines
here (except server + firewall) get powered off at night, and the remote
x86 boxen I've used in the past for occasional build testing are now under
a relatively heavy FTP (vsftp), rsync and web load and would severely
suffer from BK's consistency checks (l/a 0.91 1.32 1.76, blocks
in: ~2500 blocks/sec average.)
On bugme stuff, if you've submitted any ARM related bugs, I haven't had
any notifications from bugzilla about them (so I've not looked at bugme
since talking to Manfred. Maybe Manfred missed settings things up.)
--
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:[~2002-12-04 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 7:24 lkml, bugme.osdl.org? Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones
2002-12-03 14:13 ` bill davidsen
2002-12-03 18:09 ` Tupshin Harper
2002-12-04 11:58 ` Dr. David Alan Gilbert
2002-12-04 12:35 ` Russell King [this message]
2002-12-04 12:42 ` Dave Jones
2002-12-04 18:32 ` Dr. David Alan Gilbert
2002-12-04 22:20 ` Russell King
2002-12-05 9:15 ` David Woodhouse
2002-12-05 9:25 ` William Lee Irwin III
2002-12-05 9:34 ` David Woodhouse
2002-12-05 9:35 ` William Lee Irwin III
2002-12-05 14:24 ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh
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=20021204123517.A3563@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davej@codemonkey.org.uk \
--cc=gilbertd@treblig.org \
--cc=linux-kernel@vger.kernel.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.