public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	<JBottomley@odin.com>, <robh+dt@kernel.org>, <pawel.moll@arm.com>,
	<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
	<galak@codeaurora.org>, <arnd@arndb.de>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linuxarm@huawei.com>,
	<john.garry2@mail.dcu.ie>, <hare@suse.de>, <xuwei5@hisilicon.com>,
	<zhangfei.gao@linaro.org>
Subject: Re: [PATCH v5 00/32] HiSilicon SAS driver
Date: Wed, 18 Nov 2015 22:15:17 -0500	[thread overview]
Message-ID: <yq1io4yptmi.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <564CB40B.1050705@huawei.com> (John Garry's message of "Wed, 18 Nov 2015 17:23:23 +0000")

>>>>> "John" == John Garry <john.garry@huawei.com> writes:

John> thanks, please note that we still have the dependency on
John> http://www.spinics.net/lists/arm-kernel/msg452833.html

John> Without it the driver can only be built into the kernel, and not
John> as a module.

I have your driver in a staging branch rather than the main 4.5 SCSI
queue because I wanted to see what kind of additional fallout I'd get
from the zeroday testing.

It's not a problem for me to wait for that patch to go in (or take it
through SCSI if that makes things easier).

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2015-11-19  3:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 16:50 [PATCH v5 00/32] HiSilicon SAS driver John Garry
2015-11-17 16:50 ` [PATCH v5 01/32] [SCSI] sas: centralise ssp frame information units John Garry
2015-11-17 16:50 ` [PATCH v5 02/32] devicetree: bindings: scsi: HiSi SAS John Garry
2015-11-17 16:50 ` [PATCH v5 03/32] scsi: hisi_sas: add initial bare main driver John Garry
2015-11-17 16:50 ` [PATCH v5 04/32] scsi: hisi_sas: add scsi host registration John Garry
2015-11-17 16:50 ` [PATCH v5 05/32] scsi: hisi_sas: scan device tree John Garry
2015-11-17 16:50 ` [PATCH v5 06/32] scsi: hisi_sas: add HW DMA structures John Garry
2015-11-17 16:50 ` [PATCH v5 07/32] scsi: hisi_sas: allocate memories and create pools John Garry
2015-11-17 16:50 ` [PATCH v5 08/32] scsi: hisi_sas: add hisi_sas_remove John Garry
2015-11-17 16:50 ` [PATCH v5 09/32] scsi: hisi_sas: add slot init code John Garry
2015-11-17 16:50 ` [PATCH v5 10/32] scsi: hisi_sas: add cq structure initialization John Garry
2015-11-17 16:50 ` [PATCH v5 11/32] scsi: hisi_sas: add phy SAS ADDR initialization John Garry
2015-11-17 16:50 ` [PATCH v5 12/32] scsi: hisi_sas: set dev DMA mask John Garry
2015-11-17 16:50 ` [PATCH v5 13/32] scsi: hisi_sas: add hisi_hba workqueue John Garry
2015-11-17 16:50 ` [PATCH v5 14/32] scsi: hisi_sas: add hisi sas device type John Garry
2015-11-17 16:50 ` [PATCH v5 15/32] scsi: hisi_sas: add phy and port init John Garry
2015-11-17 16:50 ` [PATCH v5 16/32] scsi: hisi_sas: add timer and spinlock init John Garry
2015-11-17 16:50 ` [PATCH v5 17/32] scsi: hisi_sas: add v1 hw module init John Garry
2015-11-17 16:50 ` [PATCH v5 18/32] scsi: hisi_sas: add v1 hardware register definitions John Garry
2015-11-17 16:50 ` [PATCH v5 19/32] scsi: hisi_sas: add v1 HW initialisation code John Garry
2015-11-17 16:50 ` [PATCH v5 20/32] scsi: hisi_sas: add v1 hw interrupt init John Garry
2015-11-18 15:26   ` Rob Herring
2015-11-18 16:13     ` John Garry
2015-11-17 16:50 ` [PATCH v5 21/32] scsi: hisi_sas: add path from phyup irq to SAS framework John Garry
2015-11-17 16:50 ` [PATCH v5 22/32] scsi: hisi_sas: add ssp command function John Garry
2015-11-17 16:50 ` [PATCH v5 23/32] scsi: hisi_sas: add cq interrupt handler John Garry
2015-11-17 16:50 ` [PATCH v5 24/32] scsi: hisi_sas: add dev_found and dev_gone John Garry
2015-11-17 16:50 ` [PATCH v5 25/32] scsi: hisi_sas: add abnormal irq handler John Garry
2015-11-17 16:50 ` [PATCH v5 26/32] scsi: hisi_sas: add bcast interrupt handler John Garry
2015-11-17 16:50 ` [PATCH v5 27/32] scsi: hisi_sas: add smp protocol support John Garry
2015-11-17 16:50 ` [PATCH v5 28/32] scsi: hisi_sas: add scan finished and start John Garry
2015-11-17 16:50 ` [PATCH v5 29/32] scsi: hisi_sas: add tmf methods John Garry
2015-11-17 16:50 ` [PATCH v5 30/32] scsi: hisi_sas: add control phy handler John Garry
2015-11-17 16:50 ` [PATCH v5 31/32] scsi: hisi_sas: add fatal irq handler John Garry
2015-11-17 16:50 ` [PATCH v5 32/32] MAINTAINERS: add maintainer for HiSi SAS driver John Garry
2015-11-18 16:56 ` [PATCH v5 00/32] HiSilicon " Martin K. Petersen
     [not found]   ` <564CB40B.1050705@huawei.com>
2015-11-19  3:15     ` Martin K. Petersen [this message]
2015-11-19  9:46       ` 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=yq1io4yptmi.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=JBottomley@odin.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=hare@suse.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --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=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=xuwei5@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox