From: David Mosberger <davidm@napali.hpl.hp.com>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: milstone reached: ia64 linux builds out of Linus' tree
Date: Mon, 4 Aug 2003 16:35:32 -0700 [thread overview]
Message-ID: <16174.60868.750901.704560@napali.hpl.hp.com> (raw)
In-Reply-To: <16174.59114.386209.649300@wombat.chubb.wattle.id.au>
>>>>> On Tue, 5 Aug 2003 09:06:18 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:
>>>>> "David" == David Mosberger <davidm@napali.hpl.hp.com> writes:
David> Now that Linus' tree works for ia64, the next question is how
David> we can keep it that way. I think it would be useful to have
David> someone setup a cron job which does daily builds/automated
David> tests off of Linus tree. If something breaks, the person doing
David> this could perhaps come up with a minimal patch which gets
David> Linus' tree to build again (and submit a patch to the
David> appropriate maintainer, with cc to the linux-ia64 list). I
David> plan on continuing to put out roughly monthly ia64-specific
David> patches and during those normal cycles, I'd then integrate the
David> "quick fix up" patches as needed. Does this sound reasonable?
David> Anybody want to volunteer for this "Linus watchdog" role?
Peter> We can do this. We're tracking Linus's tree anyway for the work we're
Peter> doing.
Excellent!
Peter> We'd probably do daily automated builds to check that the kernel
Peter> still compiles cleanly for HPSIM, DIG, and ZX1, but test only weekly.
Sounds reasonable. Except doing a boot/halt cycle on the simulator
should be easy to automate, no? The simulator can actually catch a
surprising number of problems.
Peter> If you have anyu specific configuration options you think should be
Peter> included, let us know.
Nothing in particular, though it would be good to cover UP, MP, 16,
and 64KB page sizes (not in all permutations, of course).
Thanks,
--david
next prev parent reply other threads:[~2003-08-04 23:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 17:37 milstone reached: ia64 linux builds out of Linus' tree David Mosberger
2003-08-04 17:53 ` H. J. Lu
2003-08-04 18:00 ` Jesse Barnes
2003-08-04 18:10 ` H. J. Lu
2003-08-04 18:52 ` Jesse Barnes
2003-08-04 19:18 ` Andreas Schwab
2003-08-04 18:27 ` David Mosberger
2003-08-04 18:49 ` Jesse Barnes
2003-08-04 18:21 ` David Mosberger
2003-08-04 18:41 ` Jes Sorensen
2003-08-04 18:31 ` David S. Miller
2003-08-04 18:40 ` David Mosberger
2003-08-04 18:45 ` David S. Miller
2003-08-04 19:07 ` Alan Cox
2003-08-04 19:17 ` David S. Miller
2003-08-04 23:06 ` Peter Chubb
2003-08-04 23:35 ` David Mosberger [this message]
2003-08-13 0:07 ` Ian Wienand
2003-09-10 0:53 ` Ian Wienand
2003-09-10 1:57 ` David Mosberger
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=16174.60868.750901.704560@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.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;
as well as URLs for NNTP newsgroup(s).