On Tue, 29 Nov 2016, Guenter Roeck wrote:
On Mon, Nov 14, 2016 at 10:30:30PM +0900, Stafford Horne wrote:
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
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.
Thanks for following up. One of the members of the openrisc team was able to get his key signed recently . 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 .
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
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.