From: akpm@linux-foundation.org
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, akpm@linux-foundation.org,
fujita.tomonori@lab.ntt.co.jp, linux@highpoint-tech.com
Subject: [patch 14/17] drivers/scsi/hptiop.c: fix build warning
Date: Fri, 28 Mar 2008 14:48:41 -0700 [thread overview]
Message-ID: <200803282148.m2SLmfAG012255@imap1.linux-foundation.org> (raw)
From: Andrew Morton <akpm@linux-foundation.org>
powerpc:
drivers/scsi/hptiop.c: In function 'iop_set_config_mv':
drivers/scsi/hptiop.c:395: warning: large integer implicitly truncated to unsigned type
This field is only 32-bit, so cpu_to_le64() seems wrong.
Cc: HighPoint Linux Team <linux@highpoint-tech.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/scsi/hptiop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/scsi/hptiop.c~drivers-scsi-hptiopc-fix-build-warning drivers/scsi/hptiop.c
--- a/drivers/scsi/hptiop.c~drivers-scsi-hptiopc-fix-build-warning
+++ a/drivers/scsi/hptiop.c
@@ -392,7 +392,7 @@ static int iop_set_config_mv(struct hpti
req->header.size =
cpu_to_le32(sizeof(struct hpt_iop_request_set_config));
req->header.result = cpu_to_le32(IOP_RESULT_PENDING);
- req->header.context = cpu_to_le64(IOP_REQUEST_TYPE_SET_CONFIG<<5);
+ req->header.context = cpu_to_le32(IOP_REQUEST_TYPE_SET_CONFIG<<5);
if (iop_send_sync_request_mv(hba, 0, 20000)) {
dprintk("Set config send cmd failed\n");
_
next reply other threads:[~2008-03-28 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:48 akpm [this message]
2008-03-30 17:36 ` [patch 14/17] drivers/scsi/hptiop.c: fix build warning James Bottomley
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.m2SLmfAG012255@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@highpoint-tech.com \
/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