netdev - Re: [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III network driver.

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]

Date:   Sun, 29 Apr 2018 20:33:47 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     steven.hill@...ium.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III
 network driver.

From: "Steven J. Hill" <steven.hill@...ium.com>
Date: Thu, 26 Apr 2018 18:30:10 -0500

> We want to add the Cavium OCTEON-III network driver.  But since
> interacting with the input and output queues is done via special CPU
> local memory, we also need to add support to the MIPS/Octeon
> architecture code.  Aren't SoCs nice in this way?  These are the
> prerequisite patches that are needed before the network driver can be
> merged.

I don't know if we really want all of these MIPS specific changes to
go via the net-next tree.

The right way to do this is probably getting this series into the MIPS
architecture tree.

Then when that hits Linus's tree, and finally ends up merging into
the networking tree, you can submit the networking driver.