From: Guenter Roeck <linux@roeck-us.net>
To: Stafford Horne <shorne@gmail.com>
Cc: stefan.kristiansson@saunalahti.fi, jonas@southpole.se,
blue@cmd.nu, robh@kernel.org, linux-kernel@vger.kernel.org,
openrisc@lists.librecores.org
Subject: Re: [PATCH v2 0/9] openrisc: Misc fixes from backlog
Date: Wed, 30 Nov 2016 06:21:50 -0800 [thread overview]
Message-ID: <413b5362-ad4b-0cbe-ed46-e47582d1a51c@roeck-us.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1611301932290.29569@lianli.shorne-pla.net>
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
prev parent reply other threads:[~2016-11-30 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 13:30 Stafford Horne
[not found] ` <cover.1479128947.git.shorne@gmail.com>
2016-11-14 13:30 ` [PATCH v2 1/9] openrisc: fix PTRS_PER_PGD define Stafford Horne
2016-11-14 13:30 ` [PATCH v2 2/9] openrisc: restore all regs on rt_sigreturn Stafford Horne
2016-11-14 13:30 ` [PATCH v2 3/9] openrisc: Add thread-local storage (TLS) support Stafford Horne
2016-11-14 13:30 ` [PATCH v2 4/9] openrisc: Support both old (or32) and new (or1k) toolchain Stafford Horne
2016-11-14 13:30 ` [PATCH v2 5/9] openrisc: add NR_CPUS Kconfig default value Stafford Horne
2016-11-14 13:30 ` [PATCH v2 6/9] openrisc: remove the redundant of_platform_populate Stafford Horne
2016-11-14 13:30 ` [PATCH v2 7/9] openrisc: Consolidate setup to use memblock instead of bootmem Stafford Horne
2016-11-14 13:30 ` [PATCH v2 8/9] openrisc: Updates after openrisc.net has been lost Stafford Horne
2016-11-16 7:13 ` [OpenRISC] " Olof Kindgren
2016-12-14 8:57 ` Geert Uytterhoeven
2016-12-14 11:44 ` Stafford Horne
2016-11-14 13:30 ` [PATCH v2 9/9] openrisc: include l.swa in check for write data pagefault Stafford Horne
2016-11-30 1:23 ` [PATCH v2 0/9] openrisc: Misc fixes from backlog Guenter Roeck
2016-11-30 12:40 ` Stafford Horne
2016-11-30 14:21 ` Guenter Roeck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413b5362-ad4b-0cbe-ed46-e47582d1a51c@roeck-us.net \
--to=linux@roeck-us.net \
--cc=blue@cmd.nu \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=robh@kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®