All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-next@vger.kernel.org, Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: linux-next: sched tree build warning
Date: Tue, 21 Apr 2009 15:51:26 +0930	[thread overview]
Message-ID: <200904211551.27515.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090421102706.e19240a0.sfr@canb.auug.org.au>

On Tue, 21 Apr 2009 09:57:06 am Stephen Rothwell wrote:
> Should this call to first_cpu be cpumask_first?

Always.  Old cpu ops should die.  (I didn't actually read this code,
but it's a truism).

Thanks,
Rusty.

  parent reply	other threads:[~2009-04-21  6:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  0:27 linux-next: sched tree build warning Stephen Rothwell
2009-04-21  3:10 ` Gautham R Shenoy
2009-04-21  3:28   ` Stephen Rothwell
2009-04-21  6:09   ` Ingo Molnar
2009-04-21  8:06   ` [tip:sched/core] sched: Replace first_cpu() with cpumask_first() in ILB nomination code tip-bot for Gautham R Shenoy
2009-04-21  6:21 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-07  1:21 linux-next: sched tree build warning Stephen Rothwell
2009-05-07  6:45 ` David Rientjes
2009-05-07  7:39   ` Ingo Molnar
2008-12-22  4:22 Stephen Rothwell
2008-12-22  6:47 ` Ingo Molnar
2008-12-22  6:49 ` Ken Chen
2008-12-22  7:04   ` Ingo Molnar
2008-12-22  7:19     ` Stephen Rothwell
2008-12-22  8:14     ` Paul Mackerras
2008-12-22  8:18       ` Ingo Molnar
2008-12-22  9:44         ` Paul Mackerras
2008-12-22 10:53           ` Ingo Molnar
2008-12-22 12:03             ` Paul Mackerras

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=200904211551.27515.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=ego@in.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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.