linux-kernel - Re: xtensa port maintenance

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]

Message-ID: <50258D88.7090903@zankel.net>
Date:	Fri, 10 Aug 2012 15:39:04 -0700
From:	Chris Zankel <chris@...kel.net>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Max Filippov <jcmvbkbc@...il.com>, linux-kernel@...r.kernel.org,
	linux-xtensa@...ux-xtensa.org, linux-next@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Marc Gauthier <marc@...silica.com>,
	Kirill Krinkin <kirill.krinkin@...il.com>
Subject: Re: xtensa port maintenance

Hi Arnd,

Given the recent renewed push for Xtensa, I'll step in to feed the 
changes upstream. We might change that in future, though.

Max has volunteered to help bring the Xtensa port up-to-date. Most of 
the recent development was done on outdated trees and never got 
submitted in true kernel-manner (i.e. small changes at a time). It's 
also important to bring the ecosystem (compilers, libraries, etc.) to 
the latest trees, and my understanding is that there's also work going 
on in that area.

I have set up a tree on github for now, and will work close with Max to 
get his changes to Stephen's linux-next tree and eventually Linus' tree. 
I think it's fine to add Max as a second maintainer, so he can help 
filtering patches.

Cheers!
-Chris

On 8/10/12 2:15 PM, Arnd Bergmann wrote:
> On Monday 06 August 2012, Max Filippov wrote:
>> I have a couple of questions regarding the path of xtensa-specific patches
>> upstream:
>>      - which git tree should they be targeted for? Should I set up a tree for
>>        pull requests, or will patches be picked up into some existing tree?
>>        (Looks like Linus' tree is the right target. AFAIK previously xtensa
>>        patches went mostly through akpm tree).
> Setting up a git tree is a good first step if you want to be the official
> maintainer, and if you want to get it included into linux-next.
>

--
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/