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: <51c26e19-e4ea-7596-1147-7d95eec9e6a9@seco.com>
Date:   Mon, 25 Jul 2022 16:15:48 -0400
From:   Sean Anderson <sean.anderson@...o.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     "David S . Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
        linuxppc-dev@...ts.ozlabs.org,
        Camelia Groza <camelia.groza@....com>,
        open list <linux-kernel@...r.kernel.org>,
        Madalin Bucur <madalin.bucur@....com>,
        linux-arm-kernel@...ts.infradead.org,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Li Yang <leoyang.li@....com>, Rob Herring <robh+dt@...nel.org>,
        devicetree@...r.kernel.org
Subject: Re: [PATCH v4 00/25] net: dpaa: Cleanups in preparation for phylink
 conversion

Hi Jakub,

On 7/25/22 4:09 PM, Jakub Kicinski wrote:
> On Mon, 25 Jul 2022 11:10:14 -0400 Sean Anderson wrote:
>> This series contains several cleanup patches for dpaa/fman. While they
>> are intended to prepare for a phylink conversion, they stand on their
>> own. This series was originally submitted as part of [1].
> 
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#tl-dr

> designate your patch to a tree - [PATCH net] or [PATCH net-next]

This should be applied to net-next. Sorry, I forgot to add this when
splitting off the series. It will be added for the next revision.

> don’t post large series (> 15 patches), break them up

These are all fairly small, incremental changes. There's no natural
breaking point, but I suppose it could be arbitrarily limited.

(there are some other notes there, but I think this series is in good
order wrt. them)

--Sean

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ