public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Mike Travis <travis@sgi.com>, Ingo Molnar <mingo@elte.hu>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [FIX REQUEST] x86: smp.h is totally confused about processor ID
Date: Sat, 11 Jul 2009 20:36:22 +0930	[thread overview]
Message-ID: <200907112036.23176.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1247299234.2678.10.camel@ht.satnam>

On Sat, 11 Jul 2009 05:30:34 pm Jaswinder Singh Rajput wrote:
> In same structure it using int, unsigned and unsigned int cpu

I prefer unsigned int, but historically it's been very loose.  FWIW, I have no 
problems with a cleanup either way.

Thanks,
Rusty.

      reply	other threads:[~2009-07-11 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  8:00 [FIX REQUEST] x86: smp.h is totally confused about processor ID Jaswinder Singh Rajput
2009-07-11 11:06 ` Rusty Russell [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=200907112036.23176.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=travis@sgi.com \
    --cc=x86@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