From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Shivasharan S <shivasharan.srikanteshwara@broadcom.com>
Cc: linux-scsi@vger.kernel.org, kashyap.desai@broadcom.com,
sumit.saxena@broadcom.com, <stable@vger.kernel.org>
Subject: Re: [PATCH] megaraid_sas: Do not use 32-bit atomic request descriptor for Ventura controllers
Date: Tue, 13 Feb 2018 21:33:14 -0500 [thread overview]
Message-ID: <yq1h8qkpafp.fsf@oracle.com> (raw)
In-Reply-To: <1518413940-1657-1-git-send-email-shivasharan.srikanteshwara@broadcom.com> (Shivasharan S.'s message of "Sun, 11 Feb 2018 21:39:00 -0800")
Shivasharan,
> Sending I/O through 32 bit descriptors to Ventura series of controller
> results in IO timeout on certain conditions.
Please address Tomas' and Hannes' comments and repost these two.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-02-14 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 5:39 [PATCH] megaraid_sas: Do not use 32-bit atomic request descriptor for Ventura controllers Shivasharan S
2018-02-13 9:44 ` Hannes Reinecke
2018-02-13 15:39 ` Tomas Henzl
2018-02-14 2:33 ` Martin K. Petersen [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=yq1h8qkpafp.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=sumit.saxena@broadcom.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