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: <CAK8P3a1Kou5sRDECxA+iaJ_soogczHPdc_QNYnBDFW6Q8kKkrw@mail.gmail.com>
Date:   Mon, 21 Oct 2019 12:33:05 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Networking <netdev@...r.kernel.org>,
        "David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH 00/10] IXP4xx networking cleanups

On Mon, Oct 21, 2019 at 2:08 AM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> This is a patch series which jams together Arnds and mine
> cleanups for the IXP4xx networking.
>
> I also have patches for device tree support but that
> requires more elaborate work, this series is some of
> mine and some of Arnds patches that is a good foundation
> for his multiplatform work and my device tree work.
>
> These are for application to the networking tree so
> that can be taken in one separate sweep.
>
> I have tested the patches for a bit using zeroday builds
> and some boots on misc IXP4xx devices and haven't run
> into any major problems. We might find some new stuff
> as a result from the new compiler coverage.
>
> The patch set also hits in the ARM tree but Arnd is
> a ARM SoC maintainer and is hereby informed :)

Thanks a lot for collecting these, it looks very good overall.

I had two minor comments for your patches and noticed one
more thing about one of mine:

> Arnd Bergmann (4):
>   wan: ixp4xx_hss: fix compile-testing on 64-bit
>   wan: ixp4xx_hss: enable compile testing
>   ptp: ixp46x: move next to ethernet driver

That subject "move next to ..." makes no sense. I don't
know what I tried to write there, but if you send a new
version, please drop the "next" or try to come up with a
better subject than what I had.

     Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ