From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] phy: qcom-ufs: Switch dependency to ARCH_QCOM
Date: Tue, 12 May 2015 20:58:32 +0530 [thread overview]
Message-ID: <55521C20.9030305@ti.com> (raw)
In-Reply-To: <cc0696254c2adcd911f1dd77c5886ba0.squirrel@www.codeaurora.org>
On Tuesday 12 May 2015 12:49 PM, ygardi at codeaurora.org wrote:
> I'd change the tag to Reviewed-by.
>
> looks-good.
>
> Reviewed-by: Yaniv Gardi <ygardi@codeaurora.org>
updated the linux-phy tree with this.
Cheers
Kishon
>
>
>> looks good.
>>
>> Acked-by: Yaniv Gardi <ygardi@codeaurora.org>
>>
>>
>>> This phy only exists on platforms under ARCH_QCOM, not ARCH_MSM.
>>>
>>> Cc: Yaniv Gardi <ygardi@codeaurora.org>
>>> Cc: Dov Levenglick <dovl@codeaurora.org>
>>> Cc: Christoph Hellwig <hch@lst.de>
>>> Cc: David Brown <davidb@codeaurora.org>
>>> Cc: Bryan Huntsman <bryanh@codeaurora.org>
>>> Cc: Daniel Walker <dwalker@fifo99.com>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>> drivers/phy/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
>>> index 2962de205ba7..9b1ff313bd51 100644
>>> --- a/drivers/phy/Kconfig
>>> +++ b/drivers/phy/Kconfig
>>> @@ -286,7 +286,7 @@ config PHY_STIH41X_USB
>>>
>>> config PHY_QCOM_UFS
>>> tristate "Qualcomm UFS PHY driver"
>>> - depends on OF && ARCH_MSM
>>> + depends on OF && ARCH_QCOM
>>> select GENERIC_PHY
>>> help
>>> Support for UFS PHY on QCOM chipsets.
>>> --
>>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>>> Forum,
>>> a Linux Foundation Collaborative Project
>>>
>>>
>>
>>
>
>
prev parent reply other threads:[~2015-05-12 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 23:11 [PATCH] phy: qcom-ufs: Switch dependency to ARCH_QCOM Stephen Boyd
2015-05-12 7:05 ` ygardi at codeaurora.org
2015-05-12 7:19 ` ygardi at codeaurora.org
2015-05-12 15:28 ` Kishon Vijay Abraham I [this message]
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=55521C20.9030305@ti.com \
--to=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).