From: "hch@lst.de" <hch@lst.de>
To: James Bottomley <jbottomley@parallels.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>, "hch@lst.de" <hch@lst.de>,
"dovl@codeaurora.org" <dovl@codeaurora.org>,
"ygardi@codeaurora.org" <ygardi@codeaurora.org>,
"kishon@ti.com" <kishon@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] phy: qcom-ufs: export symbols needed by main drivers
Date: Mon, 2 Feb 2015 17:26:48 +0100 [thread overview]
Message-ID: <20150202162648.GA20465@lst.de> (raw)
In-Reply-To: <1422891069.2103.1.camel@parallels.com>
On Mon, Feb 02, 2015 at 03:30:27PM +0000, James Bottomley wrote:
> Cc added for linux-scsi, since this is the origin of the problem. How
> important is bisectability in this? It won't affect any non-embedded
> user, since most don't build with UFS, so I can go either way on folding
> or just applying as an extra patch.
The CRYPTO_DEV_QCOM_ICE symbol was never defined in the scsi trees, and
would have needed something else from linux-next to even compile. So I
don't think the revert is a problem at all, and I'll add it to the
scsi-for-3.20 branch ASAP.
next prev parent reply other threads:[~2015-02-02 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 16:18 [PATCH] phy: qcom-ufs: export symbols needed by main drivers Arnd Bergmann
2015-02-02 14:31 ` ygardi
2015-02-02 14:37 ` Kishon Vijay Abraham I
2015-02-02 14:42 ` ygardi
2015-02-02 15:30 ` James Bottomley
2015-02-02 16:26 ` hch [this message]
2015-02-02 17:55 ` James Bottomley
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=20150202162648.GA20465@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=dovl@codeaurora.org \
--cc=jbottomley@parallels.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ygardi@codeaurora.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;
as well as URLs for NNTP newsgroup(s).