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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 10 Jan 2014 11:19:54 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Stephen Rothwell <sfr@...b.auug.org.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>,
	Magnus Damm <magnus.damm@...il.com>
Subject: Re: linux-next: manual merge of the sh tree with the tree

[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@...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?

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/