From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Dilip Kota <eswara.kota@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kishon@ti.com, robh@kernel.org, cheol.yong.kim@intel.com,
chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com,
yixin.zhu@intel.com
Subject: Re: [PATCH v3 3/3] phy: intel: Add driver support for Combophy
Date: Wed, 26 Feb 2020 16:45:30 +0200 [thread overview]
Message-ID: <20200226144530.GR10400@smile.fi.intel.com> (raw)
In-Reply-To: <20200226144147.GQ10400@smile.fi.intel.com>
On Wed, Feb 26, 2020 at 04:41:47PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 26, 2020 at 06:09:53PM +0800, Dilip Kota wrote:
> > + i = 0;
> > + fwnode_for_each_available_child_node(dev_fwnode(dev), fwnode) {
>
> > + if (i >= PHY_MAX_NUM) {
> > + fwnode_handle_put(fwnode);
> > + dev_err(dev, "Error: DT child number larger than %d\n",
> > + PHY_MAX_NUM);
> > + return -EINVAL;
> > + }
>
> Logically this part is better to put after i++; line...
Ah, dismiss this, I forgot the fwnode_handle_put() part along with amount of
accessible children.
> > + ret = intel_cbphy_iphy_dt_parse(cbphy, fwnode, i);
> > + if (ret) {
> > + fwnode_handle_put(fwnode);
> > + return ret;
> > + }
> > +
>
> > + i++;
>
> ...here.
>
> > + }
> > +
> > + return intel_cbphy_dt_sanity_check(cbphy);
> > +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-02-26 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 10:09 [PATCH v3 0/3] Add Intel ComboPhy driver Dilip Kota
2020-02-26 10:09 ` [PATCH v3 1/3] mfd: syscon: Add fwnode_to_regmap Dilip Kota
2020-02-26 10:09 ` [PATCH v3 2/3] dt-bindings: phy: Add YAML schemas for Intel Combophy Dilip Kota
2020-02-26 10:09 ` [PATCH v3 3/3] phy: intel: Add driver support for Combophy Dilip Kota
2020-02-26 14:41 ` Andy Shevchenko
2020-02-26 14:45 ` Andy Shevchenko [this message]
2020-02-27 7:52 ` Dilip Kota
2020-02-27 9:43 ` Andy Shevchenko
2020-02-28 9:20 ` Dilip Kota
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=20200226144530.GR10400@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=eswara.kota@linux.intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yixin.zhu@intel.com \
/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).