From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.5.50+ patch for the impatient...
Date: Thu, 05 Dec 2002 17:06:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805504@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805503@msgid-missing>
Thanks David. Does this mean that your 'to-linus' tree will compile?
If so, I could just use that to send out an SN update (one that
compiles, btw), otherwise I'll generate a patch against this version and
hopefully have it to you next week.
Thanks,
Jesse
On Thu, Dec 05, 2002 at 12:13:59AM -0800, David Mosberger wrote:
> For those of you who're impatiently waiting for a 2.5.xx update, I put
> a preliminary patch at:
>
> ftp://ftp.hpl.hp.com/pub/linux-ia64/patch-2.5.50-1.968-lia64.diff.gz
>
> The patch is relative to revision 1.968 of Linus' bitkeeper tree
> (which is 2.5.50 with a bunch of additional patches). Only the Ski
> simulator has been tested. Kernel modules are definitely broken at
> the moment, since the ia64-part of the in-kernel module-loader is
> missing (I don't use modules myself and in any case it may be better
> to wait until things have settled down a bit; it looks like Rich
> Henderson has convinced Rusty to make modules effectively shared
> objects).
>
> I hope to have a more complete update by the time Linus gets ready to
> relese 2.5.51. So if you're not urgently waiting for 2.5.50, you
> might want to wait till then.
>
> Enjoy,
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2002-12-05 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 8:13 [Linux-ia64] 2.5.50+ patch for the impatient David Mosberger
2002-12-05 16:19 ` Matt_Domsch
2002-12-05 17:06 ` Jesse Barnes [this message]
2002-12-05 17:08 ` David Mosberger
2002-12-05 22:50 ` Matt Domsch
2002-12-06 14:15 ` Keith Owens
2002-12-07 4: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=marc-linux-ia64-105590709805504@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox