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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[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 <horms@xxxxxxxxxxxx> wrote:
> >
> > On Wed, Jan 08, 2014 at 11:11:03PM -0800, Olof Johansson wrote:
> > >
> > > 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux