linux-kernel - Re: [PATCH v2 0/9] openrisc: Misc fixes from backlog

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, 30 Nov 2016 06:21:50 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Stafford Horne <shorne@...il.com>
Cc:     stefan.kristiansson@...nalahti.fi, jonas@...thpole.se, blue@....nu,
        robh@...nel.org, linux-kernel@...r.kernel.org,
        openrisc@...ts.librecores.org
Subject: Re: [PATCH v2 0/9] openrisc: Misc fixes from backlog

On 11/30/2016 04:40 AM, Stafford Horne wrote:
>
>
> On Tue, 29 Nov 2016, Guenter Roeck wrote:
>
>> On Mon, Nov 14, 2016 at 10:30:30PM +0900, Stafford Horne wrote:
>>> Hello,
>>>
>>> This patch is a small set of fixes from the openrisc backlog. These
>>> changes fix several issues with the openrisc build on modern tool chains
>>> and address other issues which have cropped up as the kernel has been
>>> getting updated.
>>>
>>
>> Do you plan to send those patches to Linus yourself, or do you want me to do it
>> for you this time ? If so I'd ask for the patch series to be added to -next
>> and send it to Linus after the commit window opens. Let me know.
>
> Hi Guenter,
>
> Thanks for following up. One of the members of the openrisc team was able to get his key signed recently [0].  But, it puts me at 4 levels from Linus, which may not be good enough for accepting pull requests. At the same time, I am working with one Japan kernel developer to get my key signed, but there was a minor issue when we met. I hope that can get resolved this friday when I meet again at Japan Technical Jamboree [1].
>
> You might not be interested in all of that. I will do the following:
>
>   1 Create for-next branch on the github openrisc/linux with my current
>     patch set
>   2 Send a mail to Stephen Rothwell for including in linux next
>   3 When the merge window opens either the other OpenRISC maintainer or I
>     will create a signed tag and send a pull reuest to linus.
>
> If those done work we will ask you for help.
>

Sounds good. Please copy me on 3 - this way I'll know what is going on.

Thanks,
Guenter