All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dean Nelson <dcn@sgi.com>
Cc: Tony Luck <tony.luck@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64 <linux-ia64@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next
Date: Wed, 11 Feb 2009 12:32:49 +0000	[thread overview]
Message-ID: <20090211123249.GE16535@elte.hu> (raw)
In-Reply-To: <20090209162520.GA4882@sgi.com>


* 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().
> 
> Signed-off-by: Dean Nelson <dcn@sgi.com>
> Signed-off-by: Jack Steiner <steiner@sgi.com>

Applied, thanks Dean!

Tony, since this breakage is an accidental side-effect of the x86 tree (that
has to be fixed there), mind if we carry it there?

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Dean Nelson <dcn@sgi.com>
Cc: Tony Luck <tony.luck@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64 <linux-ia64@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree
Date: Wed, 11 Feb 2009 13:32:49 +0100	[thread overview]
Message-ID: <20090211123249.GE16535@elte.hu> (raw)
In-Reply-To: <20090209162520.GA4882@sgi.com>


* 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().
> 
> Signed-off-by: Dean Nelson <dcn@sgi.com>
> Signed-off-by: Jack Steiner <steiner@sgi.com>

Applied, thanks Dean!

Tony, since this breakage is an accidental side-effect of the x86 tree (that
has to be fixed there), mind if we carry it there?

	Ingo

  parent reply	other threads:[~2009-02-11 12:32 UTC|newest]

Thread overview: 20+ 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-09 16:25 ` Dean Nelson
2009-02-10 21:25 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Andrew Morton
2009-02-10 21:25   ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Andrew Morton
2009-02-11 15:01   ` Dean Nelson
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:05       ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Ingo Molnar
2009-02-11 15:12       ` Dean Nelson
2009-02-11 15:12         ` Dean Nelson
2009-02-11 18:58       ` Luck, Tony
2009-02-11 18:58         ` Luck, Tony
2009-02-11 19:33         ` Dean Nelson
2009-02-11 19:33           ` Dean Nelson
2009-02-11 20:25         ` Ingo Molnar
2009-02-11 20:25           ` Ingo Molnar
2009-02-11 12:32 ` Ingo Molnar [this message]
2009-02-11 12:32   ` Ingo Molnar
2009-02-11 18:49   ` Luck, Tony
2009-02-11 18:49     ` 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=20090211123249.GE16535@elte.hu \
    --to=mingo@elte.hu \
    --cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.