public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dean Nelson <dcn@sgi.com>
Cc: tony.luck@intel.com, mingo@elte.hu, linux-ia64@vger.kernel.org,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next
Date: Tue, 10 Feb 2009 21:25:55 +0000	[thread overview]
Message-ID: <20090210132555.be1c1462.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090209162520.GA4882@sgi.com>

On Mon, 9 Feb 2009 10:25:20 -0600
Dean Nelson <dcn@sgi.com> wrote:

> Fix the ia64 build error that occurs in the linux-next tree by introducing
> an ia64 version of uv.h.  Additionally, clean up the usage of is_uv_system().

Would I be correct in believing that this repairs (and should be folded
into)

  commit 5b221278d61e3907a5e4104a844b63bc8bb3d43a
  Author: Ingo Molnar <mingo@elte.hu>
  Date:   Wed Jan 21 11:30:07 2009 +0100

      x86: uv cleanup, build fix #2

?

(it looks like 5b221278d61e3907a5e4104a844b63bc8bb3d43a should be
folded into something else, too.  What hath we wrought?)


  reply	other threads:[~2009-02-10 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 16:25 [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Dean Nelson
2009-02-10 21:25 ` Andrew Morton [this message]
2009-02-11 15:01   ` Dean Nelson
2009-02-11 15:05     ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Ingo Molnar
2009-02-11 15:12       ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Dean Nelson
2009-02-11 18:58       ` Luck, Tony
2009-02-11 19:33         ` Dean Nelson
2009-02-11 20:25         ` Ingo Molnar
2009-02-11 12:32 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Ingo Molnar
2009-02-11 18:49   ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Luck, Tony

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=20090210132555.be1c1462.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dcn@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tony.luck@intel.com \
    /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