From: sundeep subbaraya <sundeep.lkml@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Roopa Prabhu <roopa@nvidia.com>, Ido Schimmel <idosch@idosch.org>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Hariprasad Kelam <hkelam@marvell.com>,
Geethasowjanya Akula <gakula@marvell.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Rakesh Babu Saladi <rsaladi2@marvell.com>,
Saeed Mahameed <saeed@kernel.org>,
"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Andrew Lunn <andrew@lunn.ch>,
argeorge@cisco.com
Subject: Re: [EXT] Re: [net-next PATCH 1/2] octeontx2-pf: Add devlink param to init and de-init serdes
Date: Fri, 19 Nov 2021 19:56:51 +0530 [thread overview]
Message-ID: <CALHRZuqkGNRqigj1D5CBaCGvT8xcwzkparmUwUPMMDcp=UmuUQ@mail.gmail.com> (raw)
In-Reply-To: <20211119060958.31782ca9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Fri, Nov 19, 2021 at 7:40 PM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Fri, 19 Nov 2021 16:17:53 +0530 sundeep subbaraya wrote:
> > As said by Ido, ndo_change_proto_down with proto_down as
> > on and off is sufficient for our requirement right now. We will use
> > ndo_change_proto_down instead of devlink. Thanks everyone for
> > pitching in.
>
> ndo_change_proto_down is for software devices. Make sure you explain
> your use case well, otherwise it's going to be a nack.
Sorry new to networking stuff here. Where does the below imply it is
for software devices?
* void (*ndo_change_proto_down)(struct net_device *dev,
* bool proto_down);
* This function is used to pass protocol port error state information
* to the switch driver. The switch driver can react to the proto_down
* by doing a phys down on the associated switch port.
I will find out the use case (pinged customer again)
Thanks,
Sundeep
next prev parent reply other threads:[~2021-11-19 14:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 10:31 [net-next PATCH 0/2] Add a devlink param and documentation Subbaraya Sundeep
2021-10-27 10:31 ` [net-next PATCH 1/2] octeontx2-pf: Add devlink param to init and de-init serdes Subbaraya Sundeep
2021-10-27 15:38 ` Jakub Kicinski
[not found] ` <PH0PR18MB4671C22DB7C8E5C46647860FA1859@PH0PR18MB4671.namprd18.prod.outlook.com>
2021-10-27 16:43 ` Fw: [EXT] " sundeep subbaraya
2021-10-27 17:08 ` Jakub Kicinski
2021-10-27 18:11 ` Ido Schimmel
[not found] ` <BY3PR18MB473794E01049EC94156E2858C6859@BY3PR18MB4737.namprd18.prod.outlook.com>
2021-10-27 22:24 ` Ido Schimmel
2021-10-28 12:18 ` sundeep subbaraya
2021-10-28 13:51 ` Ido Schimmel
2021-10-30 7:25 ` sundeep subbaraya
2021-11-07 9:21 ` Ido Schimmel
2021-11-08 15:54 ` Jakub Kicinski
2021-11-11 14:51 ` Ido Schimmel
2021-11-11 16:47 ` Jakub Kicinski
2021-11-14 8:38 ` Ido Schimmel
2021-11-15 4:19 ` Roopa Prabhu
2021-11-15 15:11 ` Jakub Kicinski
2021-11-19 10:47 ` sundeep subbaraya
2021-11-19 14:09 ` Jakub Kicinski
2021-11-19 14:26 ` sundeep subbaraya [this message]
2021-11-19 14:49 ` Jakub Kicinski
2021-10-27 10:31 ` [net-next PATCH 2/2] devlink: add documentation for octeontx2 driver Subbaraya Sundeep
2021-10-27 15:39 ` Jakub Kicinski
[not found] ` <PH0PR18MB46711B24C7305B8488266C8CA1859@PH0PR18MB4671.namprd18.prod.outlook.com>
2021-10-27 17:04 ` Fw: [EXT] " sundeep subbaraya
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='CALHRZuqkGNRqigj1D5CBaCGvT8xcwzkparmUwUPMMDcp=UmuUQ@mail.gmail.com' \
--to=sundeep.lkml@gmail.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=argeorge@cisco.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=idosch@idosch.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
--cc=rsaladi2@marvell.com \
--cc=saeed@kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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).