netdev - Re: [PATCH v3 16/16] Documentation: net: octeontx2: Add RVU HW and drivers overview.

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] [day] [month] [year] [list]

Message-Id: <20191121.121738.1892792993494919439.davem@davemloft.net>
Date:   Thu, 21 Nov 2019 12:17:38 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     jakub.kicinski@...ronome.com
Cc:     sunil.kovvuri@...il.com, netdev@...r.kernel.org,
        sgoutham@...vell.com
Subject: Re: [PATCH v3 16/16] Documentation: net: octeontx2: Add RVU HW and
 drivers overview.

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Thu, 21 Nov 2019 11:23:35 -0800

> Well you didn't bother to upstream it until now. You're just pushing
> admin parts of your DPDK solution. Can you honestly be surprised the
> upstream netdev community doesn't like that?

I agree with Jakub, this is a serious problem and the whole premise of
the code being upstreamed is not acceptable.

I'm going to look really strictly at octeon submissions from this point
forward, as I'm really disappointed in what is going on here.

I will have to see explicit explanations clearly showing how upstream
usage of the driver will be done, no DPDK only stuff, no SDK only
situations, none of that.  It's simply unacceptable.