netdev - Re: [PATCH net-next 3/3] nfp: devlink: allow flashing the device via devlink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190215074429.6890e47e@cakuba.netronome.com>
Date:   Fri, 15 Feb 2019 07:44:29 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     davem@...emloft.net, netdev@...r.kernel.org,
        oss-drivers@...ronome.com, mkubecek@...e.cz, andrew@...n.ch
Subject: Re: [PATCH net-next 3/3] nfp: devlink: allow flashing the device
 via devlink

On Fri, 15 Feb 2019 11:15:14 +0100, Jiri Pirko wrote:
> > static const struct ethtool_ops nfp_net_ethtool_ops = {  
> 
> Why don't you use the compat fallback? I think you should.

You and Michal both asked the same so let me answer the first to ask :)
- if devlink is built as a module the fallback is not reachable.