From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kuba@kernel.org>, <davem@davemloft.net>,
<willemdebruijn.kernel@gmail.com>, <andrew@lunn.ch>,
<sgoutham@marvell.com>, <lcherian@marvell.com>,
<gakula@marvell.com>, <jerinj@marvell.com>, <sbhatta@marvell.com>
Subject: Re: [Patch v3 net-next 7/7] octeontx2-pf: ethtool physical link configuration
Date: Tue, 2 Feb 2021 16:48:34 -0800 [thread overview]
Message-ID: <20210202164834.00004426@intel.com> (raw)
In-Reply-To: <1612157084-101715-8-git-send-email-hkelam@marvell.com>
Hariprasad Kelam wrote:
> From: Christina Jacob <cjacob@marvell.com>
>
> Register set_link_ksetting callback with driver such that
> link configurations parameters like advertised mode,speed, duplex
> and autoneg can be configured.
>
> below command
> ethtool -s eth0 advertise 0x1 speed 10 duplex full autoneg on
>
> Signed-off-by: Christina Jacob <cjacob@marvell.com>
> Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
> Signed-off-by: Hariprasad Kelam <hkelam@marvell.com>
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2021-02-03 0:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:24 [Patch v3 net-next 0/7] ethtool support for fec and link configuration Hariprasad Kelam
2021-02-01 5:24 ` [Patch v3 net-next 1/7] octeontx2-af: forward error correction configuration Hariprasad Kelam
2021-02-03 0:43 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 2/7] octeontx2-af: Add new CGX_CMD to get PHY FEC statistics Hariprasad Kelam
2021-02-03 0:43 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 3/7] octeontx2-pf: ethtool fec mode support Hariprasad Kelam
2021-02-03 0:44 ` Jesse Brandeburg
2021-02-03 1:12 ` Jakub Kicinski
2021-02-01 5:24 ` [Patch v3 net-next 4/7] octeontx2-af: Physical link configuration support Hariprasad Kelam
2021-02-03 0:44 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 5/7] octeontx2-af: advertised link modes support on cgx Hariprasad Kelam
2021-02-03 0:45 ` Jesse Brandeburg
2022-12-01 2:02 ` Chris Packham
2022-12-02 7:56 ` Hariprasad Kelam
2021-02-01 5:24 ` [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status Hariprasad Kelam
2021-02-03 0:46 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 7/7] octeontx2-pf: ethtool physical link configuration Hariprasad Kelam
2021-02-03 0:48 ` Jesse Brandeburg [this message]
2021-02-03 0:41 ` [Patch v3 net-next 0/7] ethtool support for fec and " Jesse Brandeburg
[not found] <1612098665-187767-1-git-send-email-hkelam@marvell.com>
[not found] ` <1612098665-187767-8-git-send-email-hkelam@marvell.com>
2021-02-03 1:29 ` [Patch v3 net-next 7/7] octeontx2-pf: ethtool physical " Jakub Kicinski
2021-02-04 17:37 Hariprasad Kelam
2021-02-04 18:50 ` Jakub Kicinski
2021-02-05 14:15 Hariprasad Kelam
2021-02-05 19:25 ` Jakub Kicinski
2021-02-07 15:22 Hariprasad Kelam
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=20210202164834.00004426@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=willemdebruijn.kernel@gmail.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).