linux-kernel - Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers

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]

Date:   Tue, 14 Sep 2021 19:09:37 +0200
From:   Romain Perier <romain.perier@...il.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Daniel Palmer <daniel@...f.com>, Rob Herring <robh+dt@...nel.org>,
        Olof Johansson <olof@...om.net>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        DTML <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers

Hi,

Thank you very much and sorry for the wrong inclusion of
soc@...nel.org, it's noted for the next time.

Regards,
Romain

Le mar. 14 sept. 2021 à 17:26, Arnd Bergmann <arnd@...db.de> a écrit :
>
> On Tue, Sep 14, 2021 at 5:03 PM Daniel Palmer <daniel@...f.com> wrote:
> > On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@...db.de> wrote:
>
> > > FWIW, I'd suggest merging the MAINTAINERS file change as a
> > > bugfix for 5.15, it's generally better to do these as early as possible
> > > to make sure any patches reach all the right people.
> >
> > That makes sense.
> > Would it be possible for you to merge that single commit for me?
>
> Done, merged into arm/fixes.
>
> > Seems like that would be easier than me creating a fixes branch for a
> > single commit, sending you a PR, finding out I still don't actually
> > know how to do PR properly.. :)
> > If it's a hassle I'll do the PR though.
>
> If you only have one or two patches, sending that patch to soc@...nel.org
> is usually the easiest way anyway, unless there is a reason to keep the
> branch description separate from the patch description in the git log.
>
>       Arnd