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: <CACPK8XdX8d_=YVndzJLkt6rrA7S0NEBZ-ZZ2tg-nrrg=+CrMFA@mail.gmail.com>
Date:   Wed, 11 Apr 2018 18:54:20 +0930
From:   Joel Stanley <joel@....id.au>
To:     Arnd Bergmann <arnd@...db.de>
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 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:
>> Hey Arnd,
>>
>> On 22 February 2018 at 15:33, Joel Stanley <joel@....id.au> wrote:
>>> I am interested in all ASPEED drivers, and the previous match wasn't
>>> grabbing files in nested directories. Use N instead.
>>>
>>> Add the arm kernel mailing list so that patches get reviewed there, and
>>> the linux-aspeed list which exists only so I can use patchwork to track
>>> patches.
>>>
>>> Add Andrew as a reviewer, because he is involved in reviewing ASPEED
>>> stuff.
>>>
>>> Signed-off-by: Joel Stanley <joel@....id.au>
>>
>> can you please pick this one up? It would be great to get it into
>> fixes as Andrew and I have been missing being cc'd on stuff we would
>> have like to review.
>
> 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?

Cheers,

Joel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ