linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	Nick Bowler <nbowler@elliptictech.com>,
	linux-kernel@vger.kernel.org
Subject: Re: the maxcpus= boot parameter broke somewhere along the line
Date: Wed, 07 Mar 2012 21:11:12 +0530	[thread overview]
Message-ID: <4F578198.8060708@linux.vnet.ibm.com> (raw)
In-Reply-To: <x49mx7thabf.fsf@segfault.boston.devel.redhat.com>

On 03/06/2012 11:38 PM, Jeff Moyer wrote:

> Sasha Levin <levinsasha928@gmail.com> writes:
> 
>> I can't reproduce it locally with a 3.3-rc5 kernel.
> 
> First, thanks for looking into it.  I just did a git pull, up to -rc6,
> and the problem still persists on my machine.
>


I tried 3.3-rc4 as well as 3.3-rc6+ (last commit dac12d1). I did not
see the problem in either case.


> Again, let me know if there's anything else I can provide that would be
> helpful for debugging this.
> 


Regards,
Srivatsa S. Bhat
IBM Linux Technology Center


  reply	other threads:[~2012-03-07 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 14:59 the maxcpus= boot parameter broke somewhere along the line Jeff Moyer
2012-03-06 15:17 ` Sasha Levin
2012-03-06 16:08   ` Jeff Moyer
2012-03-06 16:48   ` Nick Bowler
2012-03-06 17:15     ` Sasha Levin
2012-03-06 18:08       ` Jeff Moyer
2012-03-07 15:41         ` Srivatsa S. Bhat [this message]
2012-03-07 19:14           ` Jeff Moyer
2012-03-09 11:22             ` Srivatsa S. Bhat
2012-04-02 14:05               ` Jeff Moyer
2012-04-02 14:32                 ` Srivatsa S. Bhat
2012-04-02 14:38                   ` Jeff Moyer
2012-04-04  7:02                     ` Srivatsa S. Bhat

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=4F578198.8060708@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=jmoyer@redhat.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@elliptictech.com \
    /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).