linux-kernel - Re: [PATCH v2] gpio: xlp: Remove Netlogic XLP variants

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: <CAMRc=MeK-q6sb093Jz8mtVrAQfe6G_NXry+tq86GQ1CVGRvyng@mail.gmail.com>
Date:   Wed, 1 Dec 2021 17:49:49 +0100
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Rob Herring <robh@...nel.org>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] gpio: xlp: Remove Netlogic XLP variants

On Wed, Dec 1, 2021 at 4:01 PM Rob Herring <robh@...nel.org> wrote:
>
> On Wed, Dec 1, 2021 at 2:25 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> >
> > On Tue, Nov 30, 2021 at 8:58 PM Rob Herring <robh@...nel.org> wrote:
> > >
> > > Netlogic XLP was removed in commit 95b8a5e0111a ("MIPS: Remove NETLOGIC
> > > support"). With those gone, the single platform left to support is
> > > Cavium ThunderX2. Remove all the Netlogic variants and DT support.
> > >
> > > For simplicity, the existing kconfig name is retained.
> > >
> > > Cc: Linus Walleij <linus.walleij@...aro.org>
> > > Cc: Bartosz Golaszewski <brgl@...ev.pl>
> > > Cc: linux-gpio@...r.kernel.org
> > > Signed-off-by: Rob Herring <robh@...nel.org>
> > > ---
> > > v2:
> > >  - Fix !OF and ACPI build errors
> > >
> >
> > Rob,
> >
> > This doesn't apply on top of v5.16-rc1. Anything I'm missing?
>
> It should, that's exactly what it is based on. You dropped v1 that you
> already applied?
>
> Rob

Ah right, didn't see that. Can you send a follow-up that applies on
top of my for-next branch?

Bart