public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Christoph Lameter <christoph@lameter.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc4-mm2 build failure
Date: Tue, 17 May 2005 10:34:37 -0700	[thread overview]
Message-ID: <844780000.1116351277@flay> (raw)
In-Reply-To: <Pine.LNX.4.62.0505171020130.10798@graphe.net>



--On Tuesday, May 17, 2005 10:20:49 -0700 Christoph Lameter <christoph@lameter.com> wrote:

> On Tue, 17 May 2005, Martin J. Bligh wrote:
> 
>> > Nope. same failure.
>> 
>> Oops. I lie. Now it gets the other failure (the panic on boot we were
>> discussing before). So yes, that patch worked.
> 
> You removed the slab patches right? So this confirms that the panic on 
> boot has nothing to do with the numa slab allocator?

Nope, not yet. I just applied your other patch.

M.


  reply	other threads:[~2005-05-17 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 21:00 2.6.12-rc4-mm2 build failure Martin J. Bligh
2005-05-16 23:07 ` Christoph Lameter
2005-05-16 23:15   ` Martin J. Bligh
2005-05-17 17:08   ` Martin J. Bligh
2005-05-17 17:09     ` Martin J. Bligh
2005-05-17 17:20       ` Christoph Lameter
2005-05-17 17:34         ` Martin J. Bligh [this message]
2005-05-18  0:04   ` Matthew Dobson
2005-05-18  0:08     ` Christoph Lameter
2005-05-18 17:24       ` Matthew Dobson
2005-05-18 17:39         ` Christoph Lameter
2005-05-19  0:55           ` Matthew Dobson
2005-05-19  3:36             ` [PATCH] fix pcibus_to_node for x86_64 Christoph Lameter
     [not found] <200505162320.j4GNKDLN002527@shell0.pdx.osdl.net>
     [not found] ` <200505170433.59091.adobriyan@gmail.com>
2005-05-17  0:39   ` 2.6.12-rc4-mm2 build failure 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=844780000.1116351277@flay \
    --to=mbligh@mbligh.org \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@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