From: Kashyap Desai <kashyap.desai@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Tomas Henzl <thenzl@redhat.com>
Cc: linux-scsi@vger.kernel.org, Sumit.Saxena@avagotech.com, "Desai,
Kashyap" <Kashyap.Desai@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
stable@vger.kernel.org, kashyap.desai@broadcom.com
Subject: RE: [PATCH v2] megaraid_sas: add an i/o barrier
Date: Thu, 11 Feb 2016 00:26:42 +0530 [thread overview]
Message-ID: <c31c2e97222cd193a87316ed46bf6ecf@mail.gmail.com> (raw)
In-Reply-To: <yq1oaboa362.fsf@sermon.lab.mkp.net>
> -----Original Message-----
> From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
> Sent: Wednesday, February 10, 2016 10:55 PM
> To: Tomas Henzl
> Cc: 'linux-scsi@vger.kernel.org'; Sumit.Saxena@avagotech.com; Desai,
> Kashyap; Uday Lingala; stable@vger.kernel.org
> Subject: Re: [PATCH v2] megaraid_sas: add an i/o barrier
>
> >>>>> "Tomas" == Tomas Henzl <thenzl@redhat.com> writes:
>
> Tomas> A barrier should be added to ensure proper ordering of memory
> Tomas> mapped writes.
>
> Tomas> V2: - added the barrier also to megasas_fire_cmd_skinny, as
> Tomas> suggested by Kashyap Desai
Reviewed-by: Kashyap Desai <kashyap.desai@broadcom.com>
Acked-by: Kashyap Desai <kashyap.desai@broadcom.com>
>
> Sumit, Kashyap: Please review this patch.
>
> --
> Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-02-10 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 14:12 [PATCH v2] megaraid_sas: add an i/o barrier Tomas Henzl
2016-02-01 20:41 ` Greg KH
2016-02-10 17:25 ` Martin K. Petersen
2016-02-10 18:56 ` Kashyap Desai [this message]
2016-02-11 0:17 ` Martin K. Petersen
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=c31c2e97222cd193a87316ed46bf6ecf@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=Kashyap.Desai@avagotech.com \
--cc=Sumit.Saxena@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=thenzl@redhat.com \
--cc=uday.lingala@avagotech.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