[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6a2be2f-3bcc-128c-35fb-1ae00940b462@mellanox.com>
Date: Thu, 22 Jun 2017 13:33:16 +0300
From: Gal Pressman <galp@...lanox.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
Gal Pressman <galp@...lanox.com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
"John W. Linville" <linville@...driver.com>,
Saeed Mahameed <saeedm@...lanox.com>,
Vidya Sagar Ravipati <vidya@...ulusnetworks.com>,
Jiri Pirko <jiri@...lanox.com>,
David Decotigny <decot@...glers.com>, kernel-team@...com
Subject: Re: [RFC PATCH net-next 1/3] ethtool: Add link down reason callback
>> + ETHTOOL_LINK_PWR_BUDGET_EXC, /* Power budget exceeded */
>> + ETHTOOL_LINK_MODULE_ADMIN_DOWN, /* Module admin down */
>> +
>> + ETHTOOL_LINK_REASONS_COUNT
>> +};
> Any enumerated list is going to get changed too often.
> Could the API just return a string?
The motivation for the enumerated list is to make this API as generic as possible and compatible
with all ethernet drivers.
Returning a string is a good idea, maybe change the vendor specific opcode to a string?
Powered by blists - more mailing lists