netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Sudarsana Reddy Kalluru <skalluru@marvell.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<aelior@marvell.com>, <mkalderon@marvell.com>
Subject: Re: [PATCH net-next 0/2] qed*: SmartAN query support
Date: Thu, 7 Feb 2019 11:54:05 -0800	[thread overview]
Message-ID: <20190207115405.02563e74@cakuba.netronome.com> (raw)
In-Reply-To: <20190207142012.4521-1-skalluru@marvell.com>

On Thu, 7 Feb 2019 06:20:10 -0800, Sudarsana Reddy Kalluru wrote:
> SmartAN feature detects the peer/cable capabilities and establishes the
> link in the best possible configuration.

It sounds familiar, I need to check with FW team, but I think we may be
doing a similar thing, and adding a common API rather than ethtool flag
would be preferable.

Could you please share a little bit more detail?  What are the
configurations this would choose between?

  parent reply	other threads:[~2019-02-07 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 14:20 [PATCH net-next 0/2] qed*: SmartAN query support Sudarsana Reddy Kalluru
2019-02-07 14:20 ` [PATCH net-next 1/2] qed: Add API for SmartAN query Sudarsana Reddy Kalluru
2019-02-07 14:20 ` [PATCH net-next 2/2] qede: Add ethtool interface " Sudarsana Reddy Kalluru
2019-02-07 19:54 ` Jakub Kicinski [this message]
2019-02-08 11:32   ` [EXT] Re: [PATCH net-next 0/2] qed*: SmartAN query support Sudarsana Reddy Kalluru
2019-02-08 16:04     ` Jakub Kicinski
2019-02-09  6:55       ` David Miller
2019-02-07 21:22 ` David Miller
2019-02-07 21:32   ` 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=20190207115405.02563e74@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=mkalderon@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=skalluru@marvell.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).