From: Hannes Reinecke <hare@suse.de>
To: John Garry <john.garry@huawei.com>,
jejb@linux.vnet.ibm.com, martin.petersen@oracle.com
Cc: linuxarm@huawei.com, john.garry2@mail.dcu.ie,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
zhangfei.gao@linaro.org
Subject: Re: [PATCH 1/3] hisi_sas: add device and slot alloc hw methods
Date: Fri, 15 Apr 2016 15:51:40 +0200 [thread overview]
Message-ID: <5710F1EC.9070004@suse.de> (raw)
In-Reply-To: <1460727398-102091-2-git-send-email-john.garry@huawei.com>
On 04/15/2016 03:36 PM, John Garry wrote:
> Add methods to use HW specific versions of
> functions to allocate slot and device.
> HW specific methods are permitted to workaround
> device id vs IPTT collision issue in v2 hw.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> drivers/scsi/hisi_sas/hisi_sas.h | 3 +++
> drivers/scsi/hisi_sas/hisi_sas_main.c | 11 +++++++++--
> 2 files changed, 12 insertions(+), 2 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-04-15 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 13:36 [PATCH 0/3] hisi_sas: device id/IPTT collision workaround John Garry
2016-04-15 13:36 ` John Garry
2016-04-15 13:36 ` [PATCH 1/3] hisi_sas: add device and slot alloc hw methods John Garry
2016-04-15 13:36 ` John Garry
2016-04-15 13:51 ` Hannes Reinecke [this message]
2016-04-15 13:36 ` [PATCH 2/3] hisi_sas: add slot_index_alloc_quirk_v2_hw() John Garry
2016-04-15 13:36 ` John Garry
2016-04-15 13:51 ` Hannes Reinecke
2016-04-15 13:36 ` [PATCH 3/3] hisi_sas: add alloc_dev_quirk_v2_hw() John Garry
2016-04-15 13:36 ` John Garry
2016-04-15 13:52 ` Hannes Reinecke
2016-04-15 13:52 ` Hannes Reinecke
2016-04-15 20:56 ` [PATCH 0/3] hisi_sas: device id/IPTT collision workaround Martin K. Petersen
2016-04-15 20:56 ` 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=5710F1EC.9070004@suse.de \
--to=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry2@mail.dcu.ie \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=zhangfei.gao@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.