linux-kernel - Re: [PATCH v2] MAINTAINERS: Update email of Tudor Ambarus

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: <20230106164751.7ddaf5c54e0a764344806848@linux-foundation.org>
Date:   Fri, 6 Jan 2023 16:47:51 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Nicolas Ferre <nicolas.ferre@...rochip.com>
Cc:     Miquel Raynal <miquel.raynal@...tlin.com>,
        Tudor Ambarus <tudor.ambarus@...aro.org>, <arnd@...db.de>,
        <richard@....at>, <krzysztof.kozlowski+dt@...aro.org>,
        <herbert@...dor.apana.org.au>, <robh+dt@...nel.org>,
        <claudiu.beznea@...rochip.com>, <broonie@...nel.org>,
        <linux-kernel@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
        <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-spi@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
        <pratyush@...nel.org>, <michael@...le.cc>,
        Tudor Ambarus <tudor.ambarus@...rochip.com>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v2] MAINTAINERS: Update email of Tudor Ambarus

On Fri, 6 Jan 2023 16:59:52 +0100 Nicolas Ferre <nicolas.ferre@...rochip.com> wrote:

> > Are MAINTAINERS changes accepted through fixes PR? I see a number of
> > experienced people in Cc:, I would like to hear from you folks, because
> > I never had to do that before. If yes, then I'll do it right away,
> > otherwise I'll apply to mtd/next. I'm all ears :)
> 
> I remember a conversation that stated that MAINTAINERS changes must land 
> in Linus' tree the quickest, because it'll just avoid confusion and 
> bouncing emails.

Yes, I always merge MAINTAINERS fixes asap.

Probably these fixes should be backported into -stable kernels also -
we don't want incorrect email addresses in *any* kernel.  But I don't
do that.