From: Michael Ellerman <michael@ellerman.id.au>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [patch] powerpc/ps3: Use hard coded values for LV1 device type
Date: Sun, 08 Feb 2009 22:29:50 +1100 [thread overview]
Message-ID: <1234092590.10240.4.camel@localhost> (raw)
In-Reply-To: <498CF52E.4040903@am.sony.com>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
On Fri, 2009-02-06 at 18:42 -0800, Geoff Levand wrote:
> Change the PS3 platform code to use hard coded numbers for its
> LV1 device types.
>
> The PS3 platform code was incorrectly using some scsi block
> constants for the device type returned from the LV1 hypervisor.
>
> Fixes build errors like these when CONFIG_BLOCK=n:
>
> In file included from include/scsi/scsi.h:12,
> from arch/powerpc/platforms/ps3/platform.h:25,
> from arch/powerpc/platforms/ps3/setup.c:36:
> include/scsi/scsi_cmnd.h:27:25: warning: "BLK_MAX_CDB" is not defined
> include/scsi/scsi_cmnd.h:28:3: error: #error MAX_COMMAND_SIZE can not be bigger than BLK_MAX_CDB
>
> Signed-off-by: Geoff Levand <geoffrey.levand@am.sony.com>
> ---
> Ben,
>
> Please send upstream for 2.6.29.
>
> -Geoff
>
> arch/powerpc/platforms/ps3/platform.h | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> --- a/arch/powerpc/platforms/ps3/platform.h
> +++ b/arch/powerpc/platforms/ps3/platform.h
> @@ -22,8 +22,6 @@
> #define _PS3_PLATFORM_H
>
> #include <linux/rtc.h>
> -#include <scsi/scsi.h>
> -
> #include <asm/ps3.h>
>
> /* htab */
> @@ -83,12 +81,12 @@ enum ps3_bus_type {
> };
>
> enum ps3_dev_type {
> - PS3_DEV_TYPE_STOR_DISK = TYPE_DISK, /* 0 */
> + PS3_DEV_TYPE_STOR_DISK = 0, /* TYPE_DISK */
> PS3_DEV_TYPE_SB_GELIC = 3,
> PS3_DEV_TYPE_SB_USB = 4,
> - PS3_DEV_TYPE_STOR_ROM = TYPE_ROM, /* 5 */
> + PS3_DEV_TYPE_STOR_ROM = 5, /* TYPE_ROM */
> PS3_DEV_TYPE_SB_GPIO = 6,
> - PS3_DEV_TYPE_STOR_FLASH = TYPE_RBC, /* 14 */
> + PS3_DEV_TYPE_STOR_FLASH = 14, /* TYPE_RBC */
This looks like you're just papering over the bug, by hardcoding the
same values that are in the scsi header. Or are they really independent,
in which case I'd say the comments are confusing.
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: 197 bytes --]
next prev parent reply other threads:[~2009-02-08 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:58 2.6.29-rc3-git9 build break : arch/powerpc/platforms/ps3/setup.o Sachin P. Sant
2009-02-07 2:42 ` [patch] powerpc/ps3: Use hard coded values for LV1 device type Geoff Levand
2009-02-07 17:41 ` Sachin P. Sant
2009-02-08 11:29 ` Michael Ellerman [this message]
2009-02-09 0:11 ` Benjamin Herrenschmidt
2009-02-09 3:59 ` James Bottomley
2009-02-10 22:46 ` Geoff Levand
2009-02-11 5:28 ` Sachin P. Sant
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=1234092590.10240.4.camel@localhost \
--to=michael@ellerman.id.au \
--cc=geoffrey.levand@am.sony.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
/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).