From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] bnxt: Don't print message, if DAC isn't connected on both ends
Date: Thu, 7 Dec 2017 10:39:04 +0100 [thread overview]
Message-ID: <20171207103904.8eda285995f3dc159cb62127@suse.de> (raw)
In-Reply-To: <CACKFLikeKypJA0V6=RP=g91S4KMVHPpVLwxO5rQkvNYs1f_FEQ@mail.gmail.com>
On Thu, 7 Dec 2017 01:24:43 -0800
Michael Chan <michael.chan@broadcom.com> wrote:
> On Thu, Dec 7, 2017 at 1:14 AM, Thomas Bogendoerfer
> <tbogendoerfer@suse.de> 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 see much
> > value in that...
> >
> The main purpose is to tell the user that the speed he selected for a
> port is no longer supported due to an incompatible speed configured on
> the other port. This is useful for the user so that he can either
> take action to change the speed or do nothing as he sees fit.
just out of curiosity what's meant my imcompatible speed on the other port ?
Does the message show up continously like in the problem case I already know ?
Thomas.
--
SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-12-07 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 12:33 [PATCH net-next] bnxt: Don't print message, if DAC isn't connected on both ends Thomas Bogendoerfer
2017-12-06 18:49 ` David Miller
2017-12-06 19:27 ` Michael Chan
2017-12-07 9:14 ` Thomas Bogendoerfer
2017-12-07 9:24 ` Michael Chan
2017-12-07 9:39 ` Thomas Bogendoerfer [this message]
2017-12-07 9:47 ` Michael Chan
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=20171207103904.8eda285995f3dc159cb62127@suse.de \
--to=tbogendoerfer@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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