All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: Sumit.Saxena@avagotech.com, linux-scsi@vger.kernel.org
Cc: stable@vger.kernel.org, martin.petersen@oracle.com,
	hch@infradead.org, jbottomley@parallels.com,
	kashyap.desai@avagotech.com
Subject: Re: [PATCH RESEND 6/7] megaraid_sas : Corrected return of wait_event from abort frame path
Date: Fri, 21 Nov 2014 14:52:08 +0100	[thread overview]
Message-ID: <546F4388.6040508@redhat.com> (raw)
In-Reply-To: <201411170958.sAH9w4GU008976@palmhbs0.lsi.com>

On 11/17/2014 10:54 AM, Sumit.Saxena@avagotech.com wrote:
> Corrected wait_event() call which was waiting for wrong completion status(0xFF).
>
> Cc: <stable@vger.kernel.org>
>
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> ---
>  drivers/scsi/megaraid/megaraid_sas_base.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c b/drivers/scsi/megaraid/megaraid_sas_base.c
> index 8262067..f11c5f3 100644
> --- a/drivers/scsi/megaraid/megaraid_sas_base.c
> +++ b/drivers/scsi/megaraid/megaraid_sas_base.c
> @@ -1007,7 +1007,7 @@ megasas_issue_blocked_abort_cmd(struct megasas_instance *instance,
>  		cpu_to_le32(upper_32_bits(cmd_to_abort->frame_phys_addr));
>  
>  	cmd->sync_cmd = 1;
> -	cmd->cmd_status = 0xFF;
> +	cmd->cmd_status = ENODATA;
>  
>  	instance->instancet->issue_dcmd(instance, cmd);
>  

Reviewed-by: Tomas Henzl <thenzl@redhat.com>


      reply	other threads:[~2014-11-21 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17  9:54 [PATCH RESEND 6/7] megaraid_sas : Corrected return of wait_event from abort frame path Sumit.Saxena
2014-11-21 13:52 ` Tomas Henzl [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=546F4388.6040508@redhat.com \
    --to=thenzl@redhat.com \
    --cc=Sumit.Saxena@avagotech.com \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --cc=kashyap.desai@avagotech.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.