linux-kernel - Re: [PATCH] MAINTAINERS: Update ASPEED entry with details

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:   Wed, 11 Apr 2018 14:05:27 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Joel Stanley <joel@....id.au>
Cc:     Olof Johansson <olof@...om.net>, linux-aspeed@...ts.ozlabs.org,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update ASPEED entry with details

On Wed, Apr 11, 2018 at 11:24 AM, Joel Stanley <joel@....id.au> wrote:
> On 11 April 2018 at 18:21, Arnd Bergmann <arnd@...db.de> wrote:
>> On Wed, Apr 11, 2018 at 6:06 AM, Joel Stanley <joel@....id.au> wrote:
>>
>> Sure, applied to the fixes branch now.
>>
>> In general, when you want a patch to be applied, please send it to
>> arm@...nel.org so we know it's for us. As a rule, I don't pick up patches
>> otherwise but assume that you are asking for feedback and/or Acks
>> but will resend it once everyone is happy with the change.
>
> Okay. Do we have these rules written down anywhere?
>
> If not, would you mind if I started a document on your behalf?

Please go ahead, we can definitely use something in Documentation/arm/
that explains our process, we don't really have anything written.

      Arnd