On Thu, Dec 7, 2017 at 1:39 AM, Thomas Bogendoerfer
wrote:
> On Thu, 7 Dec 2017 01:24:43 -0800
> Michael Chan wrote:
>
>> On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
>> wrote:
>> > well, it will print the forced
On Thu, Dec 7, 2017 at 1:39 AM, Thomas Bogendoerfer
wrote:
> On Thu, 7 Dec 2017 01:24:43 -0800
> Michael Chan wrote:
>
>> On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
>> wrote:
>> > well, it will print the forced rate, if there is one configured and -1
>> > otherwise,
>> > if the link
On Thu, 7 Dec 2017 01:24:43 -0800
Michael Chan wrote:
> On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
> wrote:
> > well, it will print the forced rate, if there is one configured and -1
> > otherwise,
> > if the link is lost or will not
On Thu, 7 Dec 2017 01:24:43 -0800
Michael Chan wrote:
> On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
> wrote:
> > well, it will print the forced rate, if there is one configured and -1
> > otherwise,
> > if the link is lost or will not come up because of a cable problem. I don't
> >
On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
wrote:
> On Wed, 6 Dec 2017 11:27:31 -0800
> Michael Chan wrote:
>
>> On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
>> wrote:
>> > bnxt driver spams logfiles with
On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
wrote:
> On Wed, 6 Dec 2017 11:27:31 -0800
> Michael Chan wrote:
>
>> On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
>> wrote:
>> > bnxt driver spams logfiles with
>> >
>> > [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no
On Wed, 6 Dec 2017 11:27:31 -0800
Michael Chan wrote:
> On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
> wrote:
> > bnxt driver spams logfiles with
> >
> > [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
> >
> >
On Wed, 6 Dec 2017 11:27:31 -0800
Michael Chan wrote:
> On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
> wrote:
> > bnxt driver spams logfiles with
> >
> > [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
> >
> > if a direct attached cable (DAC) is plugged into
On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
wrote:
> bnxt driver spams logfiles with
>
> [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
>
> if a direct attached cable (DAC) is plugged into the bnxt card and is
> unplugged on the other
On Tue, Dec 5, 2017 at 4:33 AM, Thomas Bogendoerfer
wrote:
> bnxt driver spams logfiles with
>
> [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
>
> if a direct attached cable (DAC) is plugged into the bnxt card and is
> unplugged on the other side. This patch removes
From: Thomas Bogendoerfer
Date: Tue, 5 Dec 2017 13:33:40 +0100
> bnxt driver spams logfiles with
>
> [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
>
> if a direct attached cable (DAC) is plugged into the bnxt card and is
> unplugged on the
From: Thomas Bogendoerfer
Date: Tue, 5 Dec 2017 13:33:40 +0100
> bnxt driver spams logfiles with
>
> [ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
>
> if a direct attached cable (DAC) is plugged into the bnxt card and is
> unplugged on the other side. This patch
bnxt driver spams logfiles with
[ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
if a direct attached cable (DAC) is plugged into the bnxt card and is
unplugged on the other side. This patch removes the code printing this
message, since it doesn't provide any useful
bnxt driver spams logfiles with
[ 541.003065] bnxt_en :5d:00.1 eth5: Link speed -1 no longer supported
if a direct attached cable (DAC) is plugged into the bnxt card and is
unplugged on the other side. This patch removes the code printing this
message, since it doesn't provide any useful
14 matches
Mail list logo