From: Anand Lodnoor <anand.lodnoor@broadcom.com>
To: linux-scsi@vger.kernel.org
Cc: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
kiran-kumar.kasturi@broadcom.com,
Anand Lodnoor <anand.lodnoor@broadcom.com>
Subject: [PATCH 00/11] megaraid_sas: driver updates to 07.713.01.00-rc1
Date: Fri, 3 Jan 2020 17:02:24 +0530 [thread overview]
Message-ID: <1578051155-14716-1-git-send-email-anand.lodnoor@broadcom.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1136 bytes --]
This patchset contains few enhancements and fixes in megaraid_sas driver.
Anand Lodnoor (11):
megaraid_sas: Add transition_to_ready retry logic in resume path
megaraid_sas: Set no_write_same only for Virtual Disk
megaraid_sas: Update queue_depth of SAS and NVMe devices
megaraid_sas: Don’t kill already dead adapter
megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID map is
disabled
megaraid_sas: Do not set HBA Operational if FW is not in operational
state
megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
megaraid_sas: Do not initiate OCR if controller is not in ready state
megaraid_sas: Return pended IOCTLs after 3 retries
megaraid_sas: Use Block layer API to check SCSI device in-flight IO
requests
megaraid_sas: Update driver version to 07.713.01.00-rc1
drivers/scsi/megaraid/megaraid_sas.h | 17 ++--
drivers/scsi/megaraid/megaraid_sas_base.c | 99 ++++++++++++++------
drivers/scsi/megaraid/megaraid_sas_fusion.c | 134 +++++++++++++++++++++-------
drivers/scsi/megaraid/megaraid_sas_fusion.h | 18 +++-
4 files changed, 201 insertions(+), 67 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-01-03 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 11:32 Anand Lodnoor [this message]
2020-01-03 11:32 ` [PATCH 01/11] megaraid_sas: Add transition_to_ready retry logic in resume path Anand Lodnoor
2020-01-10 6:00 ` Martin K. Petersen
2020-01-03 11:32 ` [PATCH 02/11] megaraid_sas: Set no_write_same only for Virtual Disk Anand Lodnoor
2020-01-03 11:32 ` [PATCH 03/11] megaraid_sas: Update queue_depth of SAS and NVMe devices Anand Lodnoor
2020-01-10 6:03 ` Martin K. Petersen
2020-01-03 11:32 ` =?y?q?=5BPATCH=2004/11=5D=20megaraid=5Fsas=3A=20Don=E2=80=99t=20kill=20already=20dead=20adapter?= Anand Lodnoor
2020-01-10 6:03 ` .PATCH.04/11.megaraid.sas.Don.t.kill.already.dead.adapter Martin K. Petersen
2020-01-03 11:32 ` [PATCH 05/11] megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID map is disabled Anand Lodnoor
2020-01-03 11:32 ` [PATCH 06/11] megaraid_sas: Do not set HBA Operational if FW is not in operational state Anand Lodnoor
2020-01-03 11:32 ` [PATCH 07/11] megaraid_sas: Re-Define enum DCMD_RETURN_STATUS Anand Lodnoor
2020-01-03 11:32 ` [PATCH 08/11] megaraid_sas: Do not initiate OCR if controller is not in ready state Anand Lodnoor
[not found] ` <20200104053110.9D26124649@mail.kernel.org>
2020-01-07 7:59 ` Sumit Saxena
2020-01-03 11:32 ` [PATCH 09/11] megaraid_sas: Return pended IOCTLs after 3 retries Anand Lodnoor
2020-01-03 11:32 ` [PATCH 10/11] megaraid_sas: Use Block layer API to check SCSI device in-flight IO requests Anand Lodnoor
2020-01-03 11:32 ` [PATCH 11/11] megaraid_sas: Update driver version to 07.713.01.00-rc1 Anand Lodnoor
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=1578051155-14716-1-git-send-email-anand.lodnoor@broadcom.com \
--to=anand.lodnoor@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=kiran-kumar.kasturi@broadcom.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).