[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140110125529.9843f450bf79223164031b02@canb.auug.org.au>
Date: Fri, 10 Jan 2014 12:55:29 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Simon Horman <horms@...ge.net.au>
Cc: linux-sh@...r.kernel.org, Olof Johansson <olof@...om.net>,
Paul Mundt <lethal@...ux-sh.org>,
Arnd Bergmann <arnd@...db.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bastian Hecht <hechtb@...il.com>,
Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>
Subject: Re: linux-next: manual merge of the sh tree with the tree
Hi all,
On Fri, 10 Jan 2014 09:47:24 +0900 Simon Horman <horms@...ge.net.au> 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?
Is anyone maintaining/supporting sh now? Is it a candidate for pruning?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists