From: akpm@linux-foundation.org
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, akpm@linux-foundation.org,
Mark_Salyzyn@adaptec.com, aacraid@adaptec.com,
fujita.tomonori@lab.ntt.co.jp, jeff@garzik.org
Subject: [patch 12/17] ips.c: fix build warning
Date: Fri, 28 Mar 2008 14:48:40 -0700 [thread overview]
Message-ID: <200803282148.m2SLmeDg012249@imap1.linux-foundation.org> (raw)
From: Andrew Morton <akpm@linux-foundation.org>
powerpc:
drivers/scsi/ips.c: In function 'ips_issue_copperhead':
drivers/scsi/ips.c:5436: warning: large integer implicitly truncated to unsigned type
it doesn't seem necessary to do outw(cpu_to_le32(...), ...) anyway.
Acked-by: Mark Salyzyn <Mark_Salyzyn@adaptec.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: Jeff Garzik <jeff@garzik.org>
Cc: <aacraid@adaptec.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/scsi/ips.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/scsi/ips.c~ipsc-fix-build-warning drivers/scsi/ips.c
--- a/drivers/scsi/ips.c~ipsc-fix-build-warning
+++ a/drivers/scsi/ips.c
@@ -5399,7 +5399,7 @@ ips_issue_copperhead(ips_ha_t * ha, ips_
} /* end while */
outl(cpu_to_le32(scb->scb_busaddr), ha->io_addr + IPS_REG_CCSAR);
- outw(cpu_to_le32(IPS_BIT_START_CMD), ha->io_addr + IPS_REG_CCCR);
+ outw(cpu_to_le16(IPS_BIT_START_CMD), ha->io_addr + IPS_REG_CCCR);
return (IPS_SUCCESS);
}
_
next reply other threads:[~2008-03-28 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:48 akpm [this message]
2008-03-30 17:07 ` [patch 12/17] ips.c: fix build warning James Bottomley
2008-03-30 23:57 ` FUJITA Tomonori
2008-04-03 17:28 ` James Bottomley
2008-04-04 18:38 ` Mark Salyzyn
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=200803282148.m2SLmeDg012249@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Mark_Salyzyn@adaptec.com \
--cc=aacraid@adaptec.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeff@garzik.org \
--cc=linux-scsi@vger.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