netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@mellanox.com>
To: Michal Kubecek <mkubecek@suse.cz>, netdev@vger.kernel.org
Cc: Tariq Toukan <tariqt@mellanox.com>,
	"John W . Linville" <linville@tuxdriver.com>,
	Aya Levin <ayal@mellanox.com>,
	Eran Ben Elisha <eranbe@mellanox.com>
Subject: Re: [PATCH V3 ethtool] ethtool: Add support for Low Latency Reed Solomon
Date: Mon, 27 Apr 2020 16:54:31 +0300	[thread overview]
Message-ID: <2b110b9f-2b55-7064-69be-19e17dfd1b39@mellanox.com> (raw)
In-Reply-To: <20200327105108.GH31519@unicorn.suse.cz>



On 3/27/2020 1:51 PM, Michal Kubecek wrote:
> On Thu, Mar 26, 2020 at 01:09:29PM +0200, Tariq Toukan wrote:
>> From: Aya Levin <ayal@mellanox.com>
>>
>> Introduce a new FEC mode LLRS: Low Latency Reed Solomon, update print
>> and initialization functions accordingly. In addition, update related
>> man page.
>>
>> Signed-off-by: Aya Levin <ayal@mellanox.com>
>> Reviewed-by: Eran Ben Elisha <eranbe@mellanox.com>
>> Signed-off-by: Tariq Toukan <tariqt@mellanox.com>
>> ---
> 
> Reviewed-by: Michal Kubecek <mkubecek@suse.cz>
> 
> The kernel counterpart is only in net-next at the moment so that,
> technically, this should wait until after ethtool 5.6 is released.
> On the other hand, having the entry in link_modes array would improve
> compatibility with future kernels so that it would make sense to apply
> this patch now.
> 
> Michal
> 

Hi,

What is your plan for this patch?
It's not merged into master yet.

Regards,
Tariq

  reply	other threads:[~2020-04-27 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 11:09 [PATCH V3 ethtool] ethtool: Add support for Low Latency Reed Solomon Tariq Toukan
2020-03-27 10:51 ` Michal Kubecek
2020-04-27 13:54   ` Tariq Toukan [this message]
2020-05-13 19:57 ` John W. Linville

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=2b110b9f-2b55-7064-69be-19e17dfd1b39@mellanox.com \
    --to=tariqt@mellanox.com \
    --cc=ayal@mellanox.com \
    --cc=eranbe@mellanox.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 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).