linux-kernel - Re: [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers

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: <mhng-0b996c2b-86e2-4997-86ee-5510337ee460@palmer-ri-x1c9>
Date:   Thu, 02 Jun 2022 15:05:14 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...osinc.com>
To:     helgaas@...nel.org
CC:     Conor.Dooley@...rochip.com, Greg KH <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>, akpm@...ux-foundation.org,
        sboyd@...nel.org, linux-pci@...r.kernel.org,
        mturquette@...libre.com, Paul Walmsley <paul.walmsley@...ive.com>,
        kw@...ux.com, linux-clk@...r.kernel.org, aou@...s.berkeley.edu,
        lorenzo.pieralisi@....com, linux-kernel@...r.kernel.org,
        linux-riscv@...ts.infradead.org, Daire.McNamara@...rochip.com,
        Lewis.Hanly@...rochip.com, Cyril.Jean@...rochip.com,
        robh@...nel.org
Subject:     Re: [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers

On Thu, 02 Jun 2022 09:31:52 PDT (-0700), helgaas@...nel.org wrote:
> On Thu, Jun 02, 2022 at 04:39:08AM +0000, Conor.Dooley@...rochip.com wrote:
>> On 02/06/2022 02:55, Palmer Dabbelt wrote:
>
>> > I'm adding a bunch of subsystem maintainers just to check again.  I
>> > don't have any problem with it, just not really a RISC-V thing and don't
>> > wan to make a mess.  I've stashed it over at palmer/pcsoc-maintainers
>> > for now.
>> >
>> > Sorry if I'm being overly pedantic about this one...
>>
>> I don't mind. Maybe this should go via Andrew next cycle or w/e?
>> There's obviously no hurry etc
>
> My turn to be overly pedantic :)  IMHO there's no benefit in delaying
> MAINTAINERS updates.  There's zero risk, and delaying only means
> people will miss out on bug reports and other things they should learn
> about.

If by "delay" you mean wait until a merge window, then I definately 
agree -- that's just more cofusing for folks to have defacto 
maintainership outside of the tree, might as well get these in.  It's 
not like a MAINTAINERS update is going to introduce a regression or 
anything.

I'm just delaying because I just want to wait to make sure folks from 
the subsystems are OK with the updates, as these aren't really anything 
to do with RISC-V so it's not really my decision to make.