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
Subject: Re: [PATCH 00/14] megaraid_sas: driver updates
Date: Wed, 10 Jan 2018 23:21:36 -0500 [thread overview]
Message-ID: <yq17espt48f.fsf@oracle.com> (raw)
In-Reply-To: <1515158869-26693-1-git-send-email-shivasharan.srikanteshwara@broadcom.com> (Shivasharan S.'s message of "Fri, 5 Jan 2018 05:27:35 -0800")
Shivasharan,
> Shivasharan S (14):
> megaraid_sas: zero out IOC INIT and stream detection memory
> megaraid_sas: memset IOC INIT frame using correct size
> megaraid_sas: Return the DCMD status from megasas_get_seq_num
> megaraid_sas: Reset ldio_outstanding in megasas_resume
> megaraid_sas: Error handling for invalid ldcount provided by firmware
> in RAID map
> megaraid_sas: unload flag should be set after scsi_remove_host is
> called
> megaraid_sas: Avoid firing DCMDs while OCR is in progress
> megaraid_sas: Use megasas_wait_for_adapter_operational to detect
> controller state in IOCTL path
> megaraid_sas: Update LD map after populating drv_map driver map copy
> megaraid_sas: Selectively apply stream detection based on IO type
> megaraid_sas: Expose fw_cmds_outstanding through sysfs
> megaraid_sas: re-work DCMD refire code
> megaraid_sas: NVME passthru command support
> megaraid_sas: driver version upgrade
Applied to 1-12,14 to 4.16/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-01-11 4:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 13:27 [PATCH 00/14] megaraid_sas: driver updates Shivasharan S
2018-01-05 13:27 ` [PATCH 01/14] megaraid_sas: zero out IOC INIT and stream detection memory Shivasharan S
2018-01-05 13:27 ` [PATCH 02/14] megaraid_sas: memset IOC INIT frame using correct size Shivasharan S
2018-01-05 13:27 ` [PATCH 03/14] megaraid_sas: Return the DCMD status from megasas_get_seq_num Shivasharan S
2018-01-05 13:27 ` [PATCH 04/14] megaraid_sas: Reset ldio_outstanding in megasas_resume Shivasharan S
2018-01-05 13:27 ` [PATCH 05/14] megaraid_sas: Error handling for invalid ldcount provided by firmware in RAID map Shivasharan S
2018-01-05 13:27 ` [PATCH 06/14] megaraid_sas: unload flag should be set after scsi_remove_host is called Shivasharan S
2018-01-05 13:27 ` [PATCH 07/14] megaraid_sas: Avoid firing DCMDs while OCR is in progress Shivasharan S
2018-01-05 13:27 ` [PATCH 08/14] megaraid_sas: Use megasas_wait_for_adapter_operational to detect controller state in IOCTL path Shivasharan S
2018-01-05 13:27 ` [PATCH 09/14] megaraid_sas: Update LD map after populating drv_map driver map copy Shivasharan S
2018-01-05 13:27 ` [PATCH 10/14] megaraid_sas: Selectively apply stream detection based on IO type Shivasharan S
2018-01-05 13:27 ` [PATCH 11/14] megaraid_sas: Expose fw_cmds_outstanding through sysfs Shivasharan S
2018-01-05 13:27 ` [PATCH 12/14] megaraid_sas: re-work DCMD refire code Shivasharan S
2018-01-05 13:27 ` [PATCH 13/14] megaraid_sas: NVME passthru command support Shivasharan S
2018-01-05 13:27 ` [PATCH 14/14] megaraid_sas: driver version upgrade Shivasharan S
2018-01-11 4:21 ` 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=yq17espt48f.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=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).