public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Brian Uhrain <buhrain@rosettastone.com>,
	Tomi Lapinlampi <lapinlam@vega.lnet.lut.fi>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.6 ( - 2.6.16.11 ) compile failure on an alpha
Date: Tue, 25 Apr 2006 12:44:07 -0700	[thread overview]
Message-ID: <20060425194407.GA23288@suse.de> (raw)
In-Reply-To: <20060425185340.GH25520@lug-owl.de>

On Tue, Apr 25, 2006 at 08:53:40PM +0200, Jan-Benedict Glaw wrote:
> On Tue, 2006-04-25 11:29:25 +0100, Brian Uhrain <buhrain@rosettastone.com> wrote:
> > ---
> >  arch/alpha/kernel/setup.c |   12 +++++++-----
> >  1 file changed, 7 insertions(+), 5 deletions(-)
> > 
> > --- linux-2.6.16.11.orig/arch/alpha/kernel/setup.c	2006-04-25 11:21:03.000000000 +0100
> > +++ linux-2.6.16.11/arch/alpha/kernel/setup.c	2006-04-25 11:22:56.557266608 +0100
> > @@ -483,11 +483,13 @@ register_cpus(void)
> >  {
> >  	int i;
> >  
> > -	for_each_possible_cpu(i) {
> > -		struct cpu *p = kzalloc(sizeof(*p), GFP_KERNEL);
> > -		if (!p)
> > -			return -ENOMEM;
> > -		register_cpu(p, i, NULL);
> > +	for (i = 0; i < NR_CPUS; i++) {
> 
> Nope.  Please implement for_each_possible_cpu(). A patch for that flew
> along right today.

Yes, that's the proper patch.  It's in my queue to add it to the -stable
queue :)

thanks,

greg k-h

      reply	other threads:[~2006-04-25 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 10:16 2.6.16.6 ( - 2.6.16.11 ) compile failure on an alpha Tomi Lapinlampi
2006-04-25 10:29 ` Brian Uhrain
2006-04-25 18:53   ` Jan-Benedict Glaw
2006-04-25 19:44     ` Greg KH [this message]

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=20060425194407.GA23288@suse.de \
    --to=gregkh@suse.de \
    --cc=buhrain@rosettastone.com \
    --cc=lapinlam@vega.lnet.lut.fi \
    --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