linux-kernel - Re: [PATCH v4 0/9] TI-Nspire cleanups

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: <1756ff9a-babc-40c6-8002-9f464e023c52@app.fastmail.com>
Date:   Wed, 02 Nov 2022 13:42:54 +0100
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Andrew Davis" <afd@...com>, "Lee Jones" <lee@...nel.org>,
        "Rob Herring" <robh+dt@...nel.org>,
        "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@...aro.org>,
        "Linus Walleij" <linus.walleij@...aro.org>,
        "Geert Uytterhoeven" <geert+renesas@...der.be>,
        "Daniel Tang" <dt.tangr@...il.com>,
        "Fabian Vogt" <fabian@...ter-vogt.de>
Cc:     devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/9] TI-Nspire cleanups

On Tue, Nov 1, 2022, at 22:57, Andrew Davis wrote:
> Hello all,
>
> This series is an extended version of the series started here[0]
> and here[1].
>
> We break out what was the first patch into one for DTS change and
> one for code changes as suggested by Krzysztof. Those are now patches
> 2 and 8 of this series (I kept the ACKs, hope that is okay).
>
> As also pointed out by Krzysztof syscon nodes need a specific
> compatible, add that as patch 1.
>
> While I was adding that, I noticed some other dtbs_check issues,
> so while here fixed some of those up too (patches 3-6).

Hi Andrew,

Thanks for the cleanup series. All of this looks reasonable to
me, but we need to decide how to merge it upstream. I can
pick up the patches directly into the soc tree once everybody
is happy with the latest version, though usually I prefer
to take the patches or pull requests from the person listed
in the MAINTAINERS file.I'm happy to

It looks like there has never been a maintainer listed for
nspire, so it would be good to fix that. Between yourself,
Daniel and Fabian, can you find one or more people that
are willing to be listed as either reviewer or maintainer
for future patches, and decide what status you want the
platform to be listed at ("Maintained" or "Odd Fixes" I
assume)?

       Arnd