Thread (5 messages) 5 messages, 3 authors, 2014-01-10

linux-next: manual merge of the sh tree with the tree

From: horms@verge.net.au (Simon Horman)
Date: 2014-01-10 02:20:00
Also in: linux-next, linux-sh, lkml

[CC Magnus]

On Fri, Jan 10, 2014 at 12:55:29PM +1100, Stephen Rothwell wrote:
Hi all,

On Fri, 10 Jan 2014 09:47:24 +0900 Simon Horman [off-list ref] wrote:
quoted
On Wed, Jan 08, 2014 at 11:11:03PM -0800, Olof Johansson wrote:
quoted
The request to merge the sh code came through Simon with claimed
agreement from SH maintainers to do so -- I didn't verify this since
they have in the past been well-coordinated. Simon?
I spoke with Paul recently and my understanding is that
he hasn't been actively working in this area for over a year now.

I guess there are some stale patches in his tree.
That is certainly what it looks like.  So, do I remove the sh{,.-current)
trees (git://github.com/pmundt/linux-sh.git#sh-{latest,fixes-for-linus})
from linux-next permanently?  Will it be cleaned up any time soon?
I think that removing it would be a good choice.
Is anyone maintaining/supporting sh now?  Is it a candidate for pruning?
Its a topic of discussion at Renesas. And I hope that someone
will be doing some form of maintenance again soon.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help