[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <99112819-c71b-9925-0625-eda024dd6259@huawei.com>
Date: Sun, 30 Jul 2017 12:59:00 +0300
From: Aviad Krawczyk <aviad.krawczyk@...wei.com>
To: Andrew Lunn <andrew@...n.ch>
CC: Joe Perches <joe@...ches.com>, <davem@...emloft.net>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<bc.y@...wei.com>, <victor.gissin@...wei.com>,
<zhaochen6@...wei.com>, <tony.qu@...wei.com>
Subject: Re: [PATCH V2 net-next 20/21] net-next/hinic: Add ethtool and stats
Hi,
I saw that netif_err is more common in code, is it preferred on netdev_err?
What is the preferred style, netif_ or netdev_?
Best Regards,
Aviad
On 7/27/2017 1:33 AM, Andrew Lunn wrote:
> On Wed, Jul 19, 2017 at 03:36:28PM +0300, Aviad Krawczyk wrote:
>> Hi Joe,
>>
>> I tried to be consistent with the comments before, that requested
>> that we will use dev_err exclude some special cases for use netif.
>>
>> We will replace the dev_err(&netdev->dev,.. to netdev_err in the
>> next fix.
>
> netdev_err() should be used when possible. You just have to be careful
> in the probe() function, before netdev exists and you get "(NULL
> net_device):" or before it is registered and you get "(unnamed
> net_device)" instead of "eth42" etc.
>
> Andrew
>
> .
>
Powered by blists - more mailing lists