From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miquel van Smoorenburg <mikevs@xs4all.net>,
linux-scsi@vger.kernel.org,
Mark Salyzyn <mark_salyzyn@adaptec.com>,
miquels@cistron.nl, Rolf Eike Beer <eike-kernel@sf-tec.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 0/4] dpt_i2o: 64 bit support (take 5)
Date: Tue, 13 May 2008 11:51:34 -0500 [thread overview]
Message-ID: <1210697494.3077.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20080512224220.5a87a119.akpm@linux-foundation.org>
On Mon, 2008-05-12 at 22:42 -0700, Andrew Morton wrote:
> On Tue, 6 May 2008 20:10:55 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > I'll let someone else ponder ia64:
> >
> > drivers/scsi/dpt_i2o.c:83: error: `PROC_IA64' undeclared here (not in a function)
> > drivers/scsi/dpt_i2o.c:83: error: initializer element is not constant
> > drivers/scsi/dpt_i2o.c:83: error: (near initialization for `DPTI_sig.dsProcessor')
>
> fyi, this is still happening.
OK, this fixes it on my ia64.
I think this fix is the best approach, since -1 and 0xff mean unknown
processor type to the management tool. The correct fix is obviously to
add the definition of PROC_IA64 to dpt/dptsig.h, but I have no idea what
the value should be.
James
---
diff --git a/drivers/scsi/dpt_i2o.c b/drivers/scsi/dpt_i2o.c
index 8508816..bfa9f09 100644
--- a/drivers/scsi/dpt_i2o.c
+++ b/drivers/scsi/dpt_i2o.c
@@ -80,7 +80,7 @@ static dpt_sig_S DPTI_sig = {
#ifdef __i386__
PROC_INTEL, PROC_386 | PROC_486 | PROC_PENTIUM | PROC_SEXIUM,
#elif defined(__ia64__)
- PROC_INTEL, PROC_IA64,
+ PROC_INTEL, -1,
#elif defined(__sparc__)
PROC_ULTRASPARC, PROC_ULTRASPARC,
#elif defined(__alpha__)
@@ -1973,7 +1973,7 @@ static void adpt_ia64_info(sysInfo_S* si)
// This is all the info we need for now
// We will add more info as our new
// managmenent utility requires it
- si->processorType = PROC_IA64;
+ si->processorType = 0xff;
}
#endif
prev parent reply other threads:[~2008-05-13 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 23:02 [PATCH 0/4] dpt_i2o: 64 bit support (take 5) Miquel van Smoorenburg
2008-05-01 23:05 ` [PATCH 1/4] dpt_i2o: use standard __init / __exit code Miquel van Smoorenburg
2008-05-02 13:18 ` Mark Salyzyn
2008-05-01 23:06 ` [PATCH 2/4] dpt_i2o: move from virt_to_bus/bus_to_virt to dma_alloc_coherent Miquel van Smoorenburg
2008-05-02 11:25 ` Rolf Eike Beer
2008-05-02 12:15 ` Miquel van Smoorenburg
2008-05-01 23:07 ` [PATCH 3/4] dpt_i2o: 64 bit support Miquel van Smoorenburg
2008-05-02 11:32 ` Rolf Eike Beer
2008-05-01 23:08 ` [PATCH 4/4] dpt_i2o: sysfs code Miquel van Smoorenburg
2008-05-02 13:28 ` Mark Salyzyn
2008-05-07 3:10 ` [PATCH 0/4] dpt_i2o: 64 bit support (take 5) Andrew Morton
2008-05-13 5:42 ` Andrew Morton
2008-05-13 16:51 ` James Bottomley [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=1210697494.3077.33.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=mikevs@xs4all.net \
--cc=miquels@cistron.nl \
--cc=rjw@sisk.pl \
/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