Subject: Re: [PATCH v2 0/9] openrisc: Misc fixes from backlog
To: Stafford Horne <shorne@gmail.com>
References: <1479130239-30707-1-git-send-email-shorne@gmail.com>
 <20161130012311.GA4833@roeck-us.net>
 <alpine.LFD.2.20.1611301932290.29569@lianli.shorne-pla.net>
Cc: stefan.kristiansson@saunalahti.fi, jonas@southpole.se, blue@cmd.nu,
        robh@kernel.org, linux-kernel@vger.kernel.org,
        openrisc@lists.librecores.org
From: Guenter Roeck <linux@roeck-us.net>
Message-ID: <413b5362-ad4b-0cbe-ed46-e47582d1a51c@roeck-us.net>
Date: Wed, 30 Nov 2016 06:21:50 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.LFD.2.20.1611301932290.29569@lianli.shorne-pla.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated_sender: linux@roeck-us.net
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net
X-AntiAbuse: Original Domain - vger.kernel.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - roeck-us.net
X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net
X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1618
Lines: 37

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