From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>,
<linuxarm@huawei.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <arnd@arndb.de>,
<hch@infradead.org>
Subject: Re: [PATCH v6 00/22] hisi_sas: hip08 support
Date: Mon, 19 Jun 2017 21:41:57 -0400 [thread overview]
Message-ID: <yq1bmpjl9ju.fsf@oracle.com> (raw)
In-Reply-To: <1497454412-91194-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Wed, 14 Jun 2017 23:33:10 +0800")
John,
> This patchset adds support for the HiSilicon SAS controller in the
> hip08 chipset.
Applied to 4.13/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-06-20 1:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 15:33 [PATCH v6 00/22] hisi_sas: hip08 support John Garry
2017-06-14 15:33 ` [PATCH v6 01/22] scsi: hisi_sas: fix timeout check in hisi_sas_internal_task_abort() John Garry
2017-06-14 15:33 ` [PATCH v6 02/22] scsi: hisi_sas: define hisi_sas_device.device_id as int John Garry
2017-06-14 15:33 ` [PATCH v6 03/22] scsi: hisi_sas: optimise the usage of hisi_hba.lock John Garry
2017-06-14 15:33 ` [PATCH v6 04/22] scsi: hisi_sas: relocate get_ata_protocol() John Garry
2017-06-14 15:33 ` [PATCH v6 05/22] scsi: hisi_sas: relocate sata_done_v2_hw() John Garry
2017-06-14 15:33 ` [PATCH v6 06/22] scsi: hisi_sas: relocate get_ncq_tag_v2_hw() John Garry
2017-06-14 15:33 ` [PATCH v6 07/22] scsi: hisi_sas: add pci_dev in hisi_hba struct John Garry
2017-06-14 15:33 ` [PATCH v6 08/22] scsi: hisi_sas: create hisi_sas_get_fw_info() John Garry
2017-06-14 15:33 ` [PATCH v6 09/22] scsi: hisi_sas: add skeleton v3 hw driver John Garry
2017-06-14 15:33 ` [PATCH v6 10/22] scsi: hisi_sas: add initialisation for v3 pci-based controller John Garry
2017-06-14 15:33 ` [PATCH v6 11/22] scsi: hisi_sas: add v3 hw init John Garry
2017-06-14 15:33 ` [PATCH v6 12/22] scsi: hisi_sas: add v3 hw PHY init John Garry
2017-06-14 15:33 ` [PATCH v6 13/22] scsi: hisi_sas: add phy up/down/bcast and channel ISR John Garry
2017-06-14 15:33 ` [PATCH v6 14/22] scsi: hisi_sas: add v3 cq interrupt handler John Garry
2017-06-14 15:33 ` [PATCH v6 15/22] scsi: hisi_sas: add v3 code to send SSP frame John Garry
2017-06-14 15:33 ` [PATCH v6 16/22] scsi: hisi_sas: add v3 code to send SMP frame John Garry
2017-06-14 15:33 ` [PATCH v6 17/22] scsi: hisi_sas: add v3 code to send ATA frame John Garry
2017-06-14 15:33 ` [PATCH v6 18/22] scsi: hisi_sas: add v3 code for itct setup and free John Garry
2017-06-14 15:33 ` [PATCH v6 19/22] scsi: hisi_sas: add v3 code to send internal abort command John Garry
2017-06-14 15:33 ` [PATCH v6 20/22] scsi: hisi_sas: add get_wideport_bitmap_v3_hw() John Garry
2017-06-14 15:33 ` [PATCH v6 21/22] scsi: hisi_sas: add v3 code to fill some more hw function pointers John Garry
2017-06-14 15:33 ` [PATCH v6 22/22] scsi: hisi_sas: modify internal abort dev flow for v3 hw John Garry
2017-06-20 1:41 ` Martin K. Petersen [this message]
2017-06-20 9:21 ` [PATCH v6 00/22] hisi_sas: hip08 support John Garry
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=yq1bmpjl9ju.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.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