From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: fixing 2.6.10 UP builds
Date: Thu, 06 Jan 2005 21:36:58 +0000 [thread overview]
Message-ID: <20050106213658.GA25747@infradead.org> (raw)
In-Reply-To: <20050106201427.GA6009@jale>
On Thu, Jan 06, 2005 at 01:14:27PM -0700, dann frazier wrote:
> Debian is putting together 2.6.10 packages, and we noticed that we still
> need to forward port Jesse's patches. Attached is the patch Ubuntu forward
> ported, and Debian is including. It would be great to get this merged upstream
> so we don't need to port it for each release.
should be mentioned it's original from Jesse Barnes (OTOH the numa.c
copyright message implies that already).
I'd like to second the request for inclusion, distributions like Debian
really need a generic UP kernel, and having to forward-port patches
everytime a new upstream release is out is extremly annoying.
> --- kernel-source-2.6.8.defconfig/arch/ia64/kernel/cyclone.c 2004-08-14 13:07:37.000000000 -0600
> +++ kernel-source-2.6.8.newupfix.defconfig/arch/ia64/kernel/cyclone.c 2004-08-15 15:49:31.000000000 -0600
> @@ -1,8 +1,6 @@
> -#include <linux/module.h>
> #include <linux/smp.h>
> #include <linux/time.h>
> #include <linux/errno.h>
> -#include <asm/io.h>
>
> /* IBM Summit (EXA) Cyclone counter code*/
> #define CYCLONE_CBAR_ADDR 0xFEB00CD0
this hunk looks bogus.
next prev parent reply other threads:[~2005-01-06 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 20:14 fixing 2.6.10 UP builds dann frazier
2005-01-06 21:31 ` Luck, Tony
2005-01-06 21:36 ` Christoph Hellwig [this message]
2005-01-06 21:54 ` Jesse Barnes
2005-01-06 21:59 ` Luck, Tony
2005-01-08 3:02 ` dann frazier
2005-01-13 0:02 ` Luck, Tony
2005-01-13 0:20 ` Jesse Barnes
2005-01-13 0:34 ` Luck, Tony
2005-01-13 0:36 ` Christoph Lameter
2005-01-13 0:50 ` Jesse Barnes
2005-01-13 0:55 ` Mark Goodwin
2005-01-13 1:42 ` Mark Goodwin
2005-01-13 8:14 ` Christoph Hellwig
2005-01-13 19:11 ` Christoph Lameter
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=20050106213658.GA25747@infradead.org \
--to=hch@infradead.org \
--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