From: "Yankejian (Hackim Yim)" <yankejian@huawei.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Yisen Zhuang <Yisen.zhuang@huawei.com>, <davem@davemloft.net>,
<robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <huangdaode@hisilicon.com>,
<liguozhu@huawei.com>, <arnd@arndb.de>, <fengguang.wu@intel.com>,
<salil.mehta@huawei.com>, <lisheng011@huawei.com>
Cc: <devicetree@vger.kernel.org>, <netdev@vger.kernel.org>,
<linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf
Date: Mon, 18 Jan 2016 19:35:38 +0800 [thread overview]
Message-ID: <569CCE0A.5010005@huawei.com> (raw)
In-Reply-To: <1452764635.2521.28.camel@linux.intel.com>
On 2016/1/14 17:43, Andy Shevchenko wrote:
> On Thu, 2016-01-14 at 11:00 +0800, Yisen Zhuang wrote:
>> 在 2016/1/13 11:14, Kejian Yan 写道:
>>> This patch replace the assoication between dsaf and enet from
>>> string
>>> matching to object reference. It requires the DTS to be updated
>>> within
>>> BIOS. Thanks god it can be done for all released boards.
>>>
>> Hi kejian,
>>
>> This patch is fine to me.
> There are few thing below.
>
>>
>>> --- a/drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c
>>> +++ b/drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c
>>> @@ -847,6 +847,7 @@ static struct hnae_ae_ops hns_dsaf_ops = {
>>> int hns_dsaf_ae_init(struct dsaf_device *dsaf_dev)
>>> {
>>> struct hnae_ae_dev *ae_dev = &dsaf_dev->ae_dev;
>>> + static atomic_t id = ATOMIC_INIT(-1);
>>>
>>> switch (dsaf_dev->dsaf_ver) {
>>> case AE_VERSION_1:
>>> @@ -858,6 +859,9 @@ int hns_dsaf_ae_init(struct dsaf_device
>>> *dsaf_dev)
>>> default:
>>> break;
>>> }
>>> +
>>> + snprintf(ae_dev->name, AE_NAME_SIZE, "%s%d",
>>> DSAF_DEVICE_NAME,
>>> + (int)atomic_inc_return(&id));
> If you bind/unbind device enough times you may get an overflow and end
> up with name of existing device (if you have 1+ of them in the system).
>
> To avoid such situation better to use IDA/IDR framework.
thanks
Best Regards
Kejian Yan
>>>
>>> --- a/drivers/net/ethernet/hisilicon/hns/hns_enet.c
>>> +++ b/drivers/net/ethernet/hisilicon/hns/hns_enet.c
>>> @@ -1802,7 +1802,7 @@ static int hns_nic_try_get_ae(struct
>>> net_device *ndev)
>>> int ret;
>>>
>>> h = hnae_get_handle(&priv->netdev->dev,
>>> - priv->ae_name, priv->port_id, NULL);
>>> + priv->ae_node, priv->port_id, NULL);
>>> if (IS_ERR_OR_NULL(h)) {
>>> ret = PTR_ERR(h);
>>> dev_dbg(priv->dev, "has not handle, register
>>> notifier!\n");
>>> @@ -1880,9 +1880,12 @@ static int hns_nic_dev_probe(struct
>>> platform_device *pdev)
>>> else
>>> priv->enet_ver = AE_VERSION_2;
>>>
>>> - ret = of_property_read_string(node, "ae-name", &priv-
>>>> ae_name);
>>> - if (ret)
>>> - goto out_read_string_fail;
> (1)
>
>>> + priv->ae_node = (void *)of_parse_phandle(node, "ae-
>>> handle", 0);
>>> + if (IS_ERR_OR_NULL(priv->ae_node)) {
>>> + ret = PTR_ERR(priv->ae_node);
>>> + dev_err(dev, "not find ae-handle\n");
>>> + goto out_read_handle_fai;
> (2)
>
>>> + }
>>>
>>> ret = of_property_read_u32(node, "port-id", &priv-
>>>> port_id);
>>> if (ret)
>>> @@ -1945,6 +1948,8 @@ static int hns_nic_dev_probe(struct
>>> platform_device *pdev)
>>>
>>> out_notify_fail:
>>> (void)cancel_work_sync(&priv->service_task);
>>> +out_read_handle_fai:
>>> +
> Redundant line
>
>>> out_read_string_fail:
> Leftover? (see (1) and (2) )
thanks.
Best Regards
Kejian Yan
next prev parent reply other threads:[~2016-01-18 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 3:14 [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf Kejian Yan
2016-01-14 3:00 ` Yisen Zhuang
2016-01-14 9:43 ` Andy Shevchenko
2016-01-18 11:35 ` Yankejian (Hackim Yim) [this message]
[not found] ` <569F2DEC.9040209@huawei.com>
2016-01-20 9:36 ` Andy Shevchenko
2016-01-20 11:10 ` Yankejian (Hackim Yim)
2016-01-15 2:28 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 3:01 Kejian Yan
2016-01-13 2:52 ` Yankejian (Hackim Yim)
2016-01-13 2:54 ` David Miller
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=569CCE0A.5010005@huawei.com \
--to=yankejian@huawei.com \
--cc=Yisen.zhuang@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=galak@codeaurora.org \
--cc=huangdaode@hisilicon.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=liguozhu@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lisheng011@huawei.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=salil.mehta@huawei.com \
--cc=will.deacon@arm.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).