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: <CAK8P3a1Xqd0LijMhoms8vdS8zNDP-r=d7i1XL=kOk606Quo-xg@mail.gmail.com>
Date:   Mon, 15 Feb 2021 15:19:58 +0100
From:   Arnd Bergmann <arnd@...nel.org>
To:     Patrice CHOTARD <patrice.chotard@...s.st.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
        "khilman@...libre.com" <khilman@...libre.com>,
        Alexandre TORGUE <alexandre.torgue@...com>
Subject: Re: [PATCH 0/3] MAINTAINERS: update STMicroelectronics email

On Mon, Feb 15, 2021 at 2:17 PM Patrice CHOTARD
<patrice.chotard@...s.st.com> wrote:
>
> Hi Arnd, Olof, Kevin
>
> What is the best way to get this series merged ?
> Do you pick it and apply it directly, or do we integrate it in the next STM32 pull request ?

I usually pick up updates to the MAINTAINERS file as bugfixes, so
either send them as part of the fixes pull request, or forward them
to soc@...nel.org to apply directly.

If you cc me on patches for a particular platform, I usually just ignore them,
unless they get sent to soc@...nel.org, and in that case I will either apply
them or ask back if they were meant for us.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ