netdev - Re: [PATCH net-next 00/15] dpaa2-switch: CPU terminated traffic and move out of staging

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:   Wed, 10 Mar 2021 16:18:01 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Ioana Ciornei <ciorneiioana@...il.com>, davem@...emloft.net,
        kuba@...nel.org, andrew@...n.ch, f.fainelli@...il.com,
        jiri@...nulli.us, ruxandra.radulescu@....com,
        netdev@...r.kernel.org, Ioana Ciornei <ioana.ciornei@....com>
Subject: Re: [PATCH net-next 00/15] dpaa2-switch: CPU terminated traffic and
 move out of staging

Hey Greg,

On Wed, Mar 10, 2021 at 03:12:57PM +0100, Greg KH wrote:
> > Ok, I am mainly interested in getting all these patches into net-next as
> > well so that other general switchdev changes do not generate conflicts.
>
> What other general switchdev changes?

During the merge window I sent some RFC patches that change the
interaction between all switchdev drivers and the bridge:
https://patchwork.kernel.org/project/netdevbpf/patch/20210224114350.2791260-17-olteanv@gmail.com/

I would like to be able to submit that patch as non-RFC (to the net-next
tree, of course) during this release cycle, and it touches the dpaa2
switch.

Let's see what the network maintainers think about dealing with this
cross-tree situation.