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] [thread-next>] [day] [month] [year] [list]

Message-Id: <201208102115.59946.arnd@arndb.de>
Date:	Fri, 10 Aug 2012 21:15:59 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Max Filippov <jcmvbkbc@...il.com>
Cc:	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>,
	Chris Zankel <chris@...kel.net>,
	Marc Gauthier <marc@...silica.com>,
	Kirill Krinkin <kirill.krinkin@...il.com>
Subject: Re: xtensa port maintenance

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.

You should also update the maintainers file to list your git tree and name,
and have Chris give you an official approval for that update. My impression
is that he is still occasionally doing work on upstream maintainance but
has moved on to other priorities now. The two of you should decide
together if you want to both be listed as maintainers or one of you
should be a primary contact and the other one doing work in the background.

>     - which mailing lists should they go to?
>       (I guess that besides linux-xtensa@...ux-xtensa.org list they should go
>       to linux-kernel@...r.kernel.org for general review. Anything else?)

There is also linux-arch, which has the architecture maintainers. You can
consult that list if you have specific questions about changes that are
going on across architectures.

What kind of changes to you expect to do to the architecture port?
Are there additional platforms you want to get supported? Do you
want to stay compatible with existing user space software, or are you
thinking about moving to the new generic system call interfaces that
would require rebuilding all user land binaries?

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