From: "Martin K. Petersen" <martin.petersen@oracle•com>
To: Thierry Reding <thierry.reding@gmail•com>
Cc: "Martin K. Petersen" <martin.petersen@oracle•com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro•org>,
vinholikatti@gmail•com, jejb@linux•vnet.ibm.com,
liwei213@huawei•com, robh+dt@kernel•org,
devicetree@vger•kernel.org, guodong.xu@linaro•org,
linux-scsi@vger•kernel.org, linux-kernel@vger•kernel.org,
amit.kucheria@linaro•org, john.stultz@linaro•org,
linux-arm-kernel@lists•infradead.org,
Wei Xu <xuwei5@hisilicon•com>,
linux-next@vger•kernel.org
Subject: Re: [PATCH v2 2/3] arm64: dts: hisilicon: hi3670: Add UFS controller support
Date: Wed, 20 Feb 2019 09:21:01 -0500 [thread overview]
Message-ID: <yq18syak0c2.fsf@oracle.com> (raw)
In-Reply-To: <20190220113508.GB7498@ulmo> (Thierry Reding's message of "Wed, 20 Feb 2019 12:35:08 +0100")
Hi Thierry,
> it looks like you picked this up into the SCSI tree (perhaps
> inadvertently). It's been causing linux-next to fail to build since
> Monday (next-20190218) because it references a phandle (&crg_rst)
> that's not available.
I dropped the offending patch from the SCSI tree yesterday. When Stephen
updates -next, things should be fine.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-02-20 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190105072859.9134-1-manivannan.sadhasivam@linaro.org>
[not found] ` <20190105072859.9134-3-manivannan.sadhasivam@linaro.org>
2019-02-20 11:35 ` [PATCH v2 2/3] arm64: dts: hisilicon: hi3670: Add UFS controller support Thierry Reding
2019-02-20 14:21 ` Martin K. Petersen [this message]
2019-04-15 16:00 ` Wei Xu
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=yq18syak0c2.fsf@oracle.com \
--to=martin.petersen@oracle$(echo .)com \
--cc=amit.kucheria@linaro$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=guodong.xu@linaro$(echo .)org \
--cc=jejb@linux$(echo .)vnet.ibm.com \
--cc=john.stultz@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=liwei213@huawei$(echo .)com \
--cc=manivannan.sadhasivam@linaro$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
--cc=thierry.reding@gmail$(echo .)com \
--cc=vinholikatti@gmail$(echo .)com \
--cc=xuwei5@hisilicon$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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