From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, vidya.chowdary@gmail.com,
dustin@cumulusnetworks.com, roopa@cumulusnetworks.com
Subject: Re: [PATCH net] net: ethtool: Add missing kernel doc for FEC parameters
Date: Sun, 22 Apr 2018 11:51:01 +0300 [thread overview]
Message-ID: <2b103771-8a7c-642d-74d3-3dc68d175a78@cogentembedded.com> (raw)
In-Reply-To: <20180421231848.17450-1-f.fainelli@gmail.com>
Hello!
On 4/22/2018 2:18 AM, Florian Fainelli wrote:
> While adding support for ethtool::get_fecparam and set_param, kernel doc for
set_fecparam.
> these functions was missed, add those.
>
> Fixes: 1a5f3da20bd9 ("net: ethtool: add support for forward error correction modes")
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-04-22 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 23:18 [PATCH net] net: ethtool: Add missing kernel doc for FEC parameters Florian Fainelli
2018-04-22 8:51 ` Sergei Shtylyov [this message]
2018-04-23 14:28 ` 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=2b103771-8a7c-642d-74d3-3dc68d175a78@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=dustin@cumulusnetworks.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=vidya.chowdary@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).