LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	rusty@rustcorp.com.au, Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start')
Date: Wed, 19 Nov 2008 13:18:17 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0811191317120.23084@quilx.com> (raw)
In-Reply-To: <20081118153346.62bf9c11.sfr@canb.auug.org.au>

On Tue, 18 Nov 2008, Stephen Rothwell wrote:

> I have applied this to linux-next today.  It is not clear to me if this
> is a fix for the cpu_alloc tree or the zero-based per_cpu area patches or
> a combination of both.  If the first, please apply this to the cpu_alloc
> tree or I will have to drop the tree.  Otherwise, let me know where it
> belongs.

Its a fix to the cpu_alloc stuff.

> Also, considering the "discussions" between Rusty and yourself, I may
> need to drop the cpu_alloc tree until they are resolved.

Just came back from the conference. Hope I can catch up with email soon.


  reply	other threads:[~2008-11-19 19:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  6:36 linux-next: Tree for November 6 Stephen Rothwell
2008-11-06 18:39 ` next-20081106: undefined reference to `__per_cpu_start' Alexey Dobriyan
2008-11-06 19:15   ` Christoph Lameter
2008-11-06 22:34     ` Alexey Dobriyan
2008-11-07 18:32       ` Christoph Lameter
2008-11-07  5:21     ` Stephen Rothwell
2008-11-07  5:44       ` Alexey Dobriyan
2008-11-07 18:28         ` Christoph Lameter
2008-11-07 18:40       ` Christoph Lameter
2008-11-18  4:33         ` linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start') Stephen Rothwell
2008-11-19 19:18           ` Christoph Lameter [this message]
2008-11-12  7:59       ` next-20081106: undefined reference to `__per_cpu_start' Geert Uytterhoeven
2008-11-12 11:18         ` Mike Frysinger
2008-11-06 18:54 ` next-20081106: perfmon on ia64 Alexey Dobriyan
2008-11-06 20:44   ` stephane eranian
2008-11-06 19:44 ` next-20081106: today's ftrace episode Alexey Dobriyan
2008-11-06 20:03   ` Steven Rostedt
2008-11-06 20:15     ` Alexey Dobriyan
2008-11-06 20:28       ` Steven Rostedt

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=Pine.LNX.4.64.0811191317120.23084@quilx.com \
    --to=cl@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).