From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Which 2.4 kernel tree I should use for ia64?
Date: Thu, 03 Feb 2005 23:27:50 +0000 [thread overview]
Message-ID: <1107473270.12618.70.camel@eeyore> (raw)
In-Reply-To: <20050203201846.GA27365@lucon.org>
On Thu, 2005-02-03 at 12:18 -0800, H. J. Lu wrote:
> I am testing the ia64 assembler changes on 2.4 and 2.6 kernel. Which
> 2.4 kernel tree should I use?
The most recent 2.4 patch for ia64 is here:
ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.4/linux-2.4.26-ia64-040510.diff.bz2
I haven't been producing 2.4 patches recently because I don't
think anyone would actually use them.
My assumption is that most people using 2.4 kernels on ia64 are
running distro kernels, and distros are only interested in backports
of specific bugfixes, not in ia64 patches for new 2.4 kernels.
If my assumption is incorrect, and somebody does care about new
ia64 patches for 2.4, please speak up!
Bjorn
next prev parent reply other threads:[~2005-02-03 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 20:18 Which 2.4 kernel tree I should use for ia64? H. J. Lu
2005-02-03 23:27 ` Bjorn Helgaas [this message]
2005-02-04 6:55 ` Christian Hildner
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=1107473270.12618.70.camel@eeyore \
--to=bjorn.helgaas@hp.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