From: Andrew Lunn <andrew@lunn.ch>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Edward Cree <ecree@solarflare.com>,
"John W. Linville" <linville@tuxdriver.com>,
netdev <netdev@vger.kernel.org>,
Ganesh Goudar <ganeshgr@chelsio.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Dustin Byford <dustin@cumulusnetworks.com>,
Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Subject: Re: [PATCH ethtool] ethtool: support combinations of FEC modes
Date: Wed, 19 Sep 2018 17:33:38 +0200 [thread overview]
Message-ID: <20180919153338.GE17466@lunn.ch> (raw)
In-Reply-To: <20180919144117.GF3876@unicorn.suse.cz>
> One loosely related question: how sure can we be that we are never going
> to need more than 32 bits for FEC encodings? Is it something completely
> hypothetical or is it something that could happen in the future?
>
Hi Michal
Hopefully we have moved to a netlink socket by that time :-)
I recently found that EEE still uses a u32 for advertise link modes.
We should fix that in the netlink API.
Andrew
next prev parent reply other threads:[~2018-09-19 21:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 17:54 [PATCH ethtool] ethtool: support combinations of FEC modes Edward Cree
2018-09-17 19:52 ` John W. Linville
2018-09-19 14:41 ` Michal Kubecek
2018-09-19 15:33 ` Andrew Lunn [this message]
2018-09-19 15:49 ` Michal Kubecek
2018-09-19 15:38 ` Edward Cree
2018-09-19 15:56 ` Michal Kubecek
2018-09-19 16:06 ` [RFC PATCH ethtool] ethtool: better syntax for " Edward Cree
2018-09-20 13:46 ` Michal Kubecek
2018-10-01 18:59 ` John W. Linville
2018-10-04 14:08 ` John W. Linville
2018-10-04 14:43 ` Michal Kubecek
2018-10-04 16:06 ` Edward Cree
2018-10-04 19:41 ` John W. Linville
[not found] ` <811cf92b-51ed-4a8f-4b69-113cdd8473df@mellanox.com>
2018-09-26 8:47 ` [PATCH ethtool] ethtool: support " Ariel Almog
2018-09-28 12:58 ` Edward Cree
2018-09-28 15:39 ` Andrew Lunn
2018-09-28 16:11 ` Edward Cree
2018-09-28 16:45 ` Andrew Lunn
2018-09-28 17:30 ` Edward Cree
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=20180919153338.GE17466@lunn.ch \
--to=andrew@lunn.ch \
--cc=dirk.vandermerwe@netronome.com \
--cc=dustin@cumulusnetworks.com \
--cc=ecree@solarflare.com \
--cc=ganeshgr@chelsio.com \
--cc=jakub.kicinski@netronome.com \
--cc=linville@tuxdriver.com \
--cc=mkubecek@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.