public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi•com>
To: Pekka J Enberg <penberg@cs•helsinki.fi>
Cc: Vegard Nossum <vegard.nossum@gmail•com>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	Steven Rostedt <srostedt@redhat•com>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for June 23
Date: Mon, 23 Jun 2008 12:21:50 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806231220470.28070@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806232155060.4033@sbz-30.cs.Helsinki.FI>

On Mon, 23 Jun 2008, Pekka J Enberg wrote:

> Christoph, while the warning itself seems harmless, I think we need to do 
> something like the following; otherwise the return value for 
> kmem_cache_defrag() will be incorrect on NUMA machines that have more than 
> one N_NORMAL_MEMORY nodes.

Patch looks to be the right fix. Thanks.

Acked-by: Christoph Lameter <clameter@sgi•com>

  reply	other threads:[~2008-06-23 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23  8:25 linux-next: Tree for June 23 Stephen Rothwell
2008-06-23 10:23 ` Vegard Nossum
2008-06-23 10:26   ` Vegard Nossum
2008-06-23 11:02     ` Vegard Nossum
2008-06-23 12:26       ` Vegard Nossum
2008-06-23 17:26         ` Vegard Nossum
2008-06-23 17:43           ` Vegard Nossum
2008-06-23 18:56       ` Pekka J Enberg
2008-06-23 19:21         ` Christoph Lameter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-23  5:33 Stephen Rothwell
2009-06-23  6:07 ` Stephen Rothwell
2010-06-23  5:45 Stephen Rothwell
2011-06-23  5:54 Stephen Rothwell
2011-06-23 10:25 ` Linus Walleij
2011-06-23 10:54   ` Stephen Rothwell

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.0806231220470.28070@schroedinger.engr.sgi.com \
    --to=clameter@sgi$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=penberg@cs$(echo .)helsinki.fi \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=srostedt@redhat$(echo .)com \
    --cc=vegard.nossum@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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