linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 7/16] powerpc: add support for ps3 platform
Date: Thu, 16 Nov 2006 13:13:01 +1100	[thread overview]
Message-ID: <1163643181.8805.19.camel@localhost.localdomain> (raw)
In-Reply-To: <455BC1E1.2010300@am.sony.com>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

On Wed, 2006-11-15 at 17:41 -0800, Geoff Levand wrote:
> Christoph Hellwig wrote:

> >> +#if !defined(PPC_MSG_MIGRATE_TASK)
> >> +static const int PPC_MSG_MIGRATE_TASK = 2;
> >> +#endif
> > 
> > This looks rather odd, what is it trying to do?
> 
> 
> For some reason the definition of PPC_MSG_MIGRATE_TASK is sometimes 2, and
> sometimes not defined, depending on other config options.  It makes the code
> much simpler if it is always defined as 2.  Maybe it makes more sense if I
> change it to this:
> 
> #if !defined(PPC_MSG_MIGRATE_TASK)
> #define PPC_MSG_MIGRATE_TASK 2
> #endif

include/asm-powerpc/smp.h says:

/* This is unused now */
#if 0
#define PPC_MSG_MIGRATE_TASK    2
#endif


So it will never be defined. Why do you need it, you don't seem to use
it anywhere?

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-16  2:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 20:02 [PATCH 7/16] powerpc: add support for ps3 platform Geoff Levand
2006-11-10 21:23 ` Olof Johansson
2006-11-14  0:11   ` Geoff Levand
2006-11-15 17:54     ` Christoph Hellwig
2006-11-21  2:50     ` Paul Mackerras
2006-11-21 10:11       ` Arnd Bergmann
2006-11-21 10:15         ` Geert Uytterhoeven
2006-11-21 11:59           ` Paul Mackerras
2006-11-21 13:22             ` Christoph Hellwig
2006-11-21 13:42               ` Arnd Bergmann
2006-11-21 13:45                 ` Christoph Hellwig
2006-11-21 19:54                   ` Geoff Levand
2006-11-21 19:54                 ` Geoff Levand
2006-11-21 19:54               ` Geoff Levand
2006-11-14 14:25   ` Geoff Levand
2006-11-11 11:21 ` Christoph Hellwig
2006-11-11 11:24   ` Christoph Hellwig
2006-11-11 11:50 ` Arnd Bergmann
2006-11-13  3:29   ` Geoff Levand
2006-11-14 14:00   ` Geoff Levand
2006-11-15 18:04 ` Christoph Hellwig
2006-11-16  1:41   ` Geoff Levand
2006-11-16  2:13     ` Michael Ellerman [this message]
2006-11-17  1:31       ` Geoff Levand
2006-11-17  6:41     ` Christoph Hellwig
2006-11-17 22:23       ` Benjamin Herrenschmidt
2006-11-18  2:02       ` Geoff Levand
2006-11-21 21:12       ` Geoff Levand
2006-11-17  0:39   ` Benjamin Herrenschmidt
2006-11-17  1:33     ` Geoff Levand
2006-11-17  1:42       ` Michael Ellerman
2006-11-17  2:04         ` Geoff Levand
2006-11-17  2:19           ` Michael Ellerman
2006-11-17  2:44             ` Geoff Levand
2006-11-16 16:35 ` Arnd Bergmann

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=1163643181.8805.19.camel@localhost.localdomain \
    --to=michael@ellerman.id.au \
    --cc=geoffrey.levand@am.sony.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).