Commit f6b196a2 authored by James Bottomley's avatar James Bottomley

[SCSI] hptiop: fix header.context usage

header.context is a 64 bit field, but it's deliberately split into
context and context_hi32.  Thus cpu_to_le64 assignments are wrong on
this.  Replace them with the correct settings of both the low and high
words.

Cc: HighPoint Linux Team <linux@highpoint-tech.com>
Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
parent a579dab1
...@@ -338,7 +338,8 @@ static int iop_get_config_mv(struct hptiop_hba *hba, ...@@ -338,7 +338,8 @@ static int iop_get_config_mv(struct hptiop_hba *hba,
req->header.size = req->header.size =
cpu_to_le32(sizeof(struct hpt_iop_request_get_config)); cpu_to_le32(sizeof(struct hpt_iop_request_get_config));
req->header.result = cpu_to_le32(IOP_RESULT_PENDING); req->header.result = cpu_to_le32(IOP_RESULT_PENDING);
req->header.context = cpu_to_le64(IOP_REQUEST_TYPE_GET_CONFIG<<5); req->header.context = cpu_to_le32(IOP_REQUEST_TYPE_GET_CONFIG<<5);
req->header.context_hi32 = 0;
if (iop_send_sync_request_mv(hba, 0, 20000)) { if (iop_send_sync_request_mv(hba, 0, 20000)) {
dprintk("Get config send cmd failed\n"); dprintk("Get config send cmd failed\n");
...@@ -392,7 +393,8 @@ static int iop_set_config_mv(struct hptiop_hba *hba, ...@@ -392,7 +393,8 @@ static int iop_set_config_mv(struct hptiop_hba *hba,
req->header.size = req->header.size =
cpu_to_le32(sizeof(struct hpt_iop_request_set_config)); cpu_to_le32(sizeof(struct hpt_iop_request_set_config));
req->header.result = cpu_to_le32(IOP_RESULT_PENDING); 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);
req->header.context_hi32 = 0;
if (iop_send_sync_request_mv(hba, 0, 20000)) { if (iop_send_sync_request_mv(hba, 0, 20000)) {
dprintk("Set config send cmd failed\n"); dprintk("Set config send cmd failed\n");
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment