On 01/23/2017 01:33 AM, maowenan wrote:
>
>
> On 2017/1/6 12:48, Florian Fainelli wrote:
>> Le 01/05/17 à 19:39, maowenan a écrit :
>>>
>>>
>>> On 2017/1/6 11:21, Florian Fainelli wrote:
+Andrew,
Le 01/05/17 à 18:29, maowenan a écrit :
>>> @Florian Fainelli, what's your comment
On 2017/1/6 12:48, Florian Fainelli wrote:
> Le 01/05/17 à 19:39, maowenan a écrit :
>>
>>
>> On 2017/1/6 11:21, Florian Fainelli wrote:
>>> +Andrew,
>>>
>>> Le 01/05/17 à 18:29, maowenan a écrit :
>> @Florian Fainelli, what's your comments about this patch?
>
> I am trying to reprodu
Le 01/05/17 à 19:39, maowenan a écrit :
>
>
> On 2017/1/6 11:21, Florian Fainelli wrote:
>> +Andrew,
>>
>> Le 01/05/17 à 18:29, maowenan a écrit :
> @Florian Fainelli, what's your comments about this patch?
I am trying to reproduce what you are seeing, but at first glance is looks
On 2017/1/6 11:21, Florian Fainelli wrote:
> +Andrew,
>
> Le 01/05/17 à 18:29, maowenan a écrit :
@Florian Fainelli, what's your comments about this patch?
>>>
>>> I am trying to reproduce what you are seeing, but at first glance is looks
>>> like an
>>> appropriate solution to me. Do you
+Andrew,
Le 01/05/17 à 18:29, maowenan a écrit :
>>> @Florian Fainelli, what's your comments about this patch?
>>
>> I am trying to reproduce what you are seeing, but at first glance is looks
>> like an
>> appropriate solution to me. Do you mind giving me a couple more days?
>>
>> Thanks!
>> --
>
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Tuesday, December 13, 2016 12:33 AM
> To: maowenan; David Laight; netdev@vger.kernel.org; Dingtianhong;
> weiyongjun (A)
> Subject: Re: [PATCH] net:phy fix driver reference count err
On 12/12/2016 12:49 AM, maowenan wrote:
>
>
> On 2016/12/5 16:47, maowenan wrote:
>>
>>
>> On 2016/12/2 17:45, David Laight wrote:
>>> From: Mao Wenan
Sent: 30 November 2016 10:23
The nic in my board use the phy dev from marvell, and the system will
load the marvell phy driver auto
On 2016/12/5 16:47, maowenan wrote:
>
>
> On 2016/12/2 17:45, David Laight wrote:
>> From: Mao Wenan
>>> Sent: 30 November 2016 10:23
>>> The nic in my board use the phy dev from marvell, and the system will
>>> load the marvell phy driver automatically, but when I remove the phy
>>> drivers, t
On 2016/12/2 17:45, David Laight wrote:
> From: Mao Wenan
>> Sent: 30 November 2016 10:23
>> The nic in my board use the phy dev from marvell, and the system will
>> load the marvell phy driver automatically, but when I remove the phy
>> drivers, the system immediately panic:
>> Call trace:
>> [
From: Mao Wenan
> Sent: 30 November 2016 10:23
> The nic in my board use the phy dev from marvell, and the system will
> load the marvell phy driver automatically, but when I remove the phy
> drivers, the system immediately panic:
> Call trace:
> [ 2582.834493] [] phy_state_machine+0x3c/0x438 [
> 2
The nic in my board use the phy dev from marvell, and the system will
load the marvell phy driver automatically, but when I remove the phy
drivers, the system immediately panic:
Call trace:
[ 2582.834493] [] phy_state_machine+0x3c/0x438 [
2582.851754] [] process_one_work+0x150/0x428 [
2582.868188]
11 matches
Mail list logo