From: Kishon Vijay Abraham I <kishon@ti.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Yaniv Gardi <ygardi@codeaurora.org>,
Dov Levenglick <dovl@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: qcom-ufs: Catch devm_phy_create failure in ufs_qcom_phy_generic_probe
Date: Tue, 17 Mar 2015 14:39:22 +0530 [thread overview]
Message-ID: <5507EF42.6000202@ti.com> (raw)
In-Reply-To: <CAFRkauB27nRLUykeEQWFWV5X2OrQAKfnCu5qY+6-kN0cvL9NUw@mail.gmail.com>
On Tuesday 17 March 2015 06:17 AM, Axel Lin wrote:
> 2015-03-03 9:05 GMT+08:00 Axel Lin <axel.lin@ingics.com>:
>> Current code does NULL test against return value of ufs_qcom_phy_generic_probe.
>> However, in the case of devm_phy_create() failure, ufs_qcom_phy_generic_probe
>> does not return NULL. Fix it.
> Hi Kishon,
> Seems this patch is missed.
> Should I resend it?
not necessary, I have the patch with me.
Thanks
Kishon
prev parent reply other threads:[~2015-03-17 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 1:05 [PATCH] phy: qcom-ufs: Catch devm_phy_create failure in ufs_qcom_phy_generic_probe Axel Lin
2015-03-17 0:47 ` Axel Lin
2015-03-17 9:09 ` 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=5507EF42.6000202@ti.com \
--to=kishon@ti.com \
--cc=axel.lin@ingics.com \
--cc=dovl@codeaurora.org \
--cc=linux-kernel@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