linux-kernel - Re: [RFC] ARM Subarchitecture group maintainership

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]

Date:	Thu, 19 May 2011 20:28:17 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Barry Song <21cnbao@...il.com>, Nicolas Pitre <nico@...xnic.net>,
	Arnd Bergmann <arnd@...db.de>,
	lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC] ARM Subarchitecture group maintainership

On Thu, May 19, 2011 at 03:31:42PM +0200, Linus Walleij wrote:
> On Thu, May 19, 2011 at 5:01 AM, Barry Song <21cnbao@...il.com> wrote:
> 
> > i asked this because we wanted to send the source codes of
> > CSR(http://www.csr.com) to upstream as i have told you in LDS. it
> > looks like we need to follow the below new changes to make our source
> > codes acceptable?
> > 1. arm device tree
> > 2. new pinmux framework from Linus Walleij
> 
> I'm working on that to post a new v3 of this patch set ASAP, if the
> ARM subarch tree maintainers are interested I can send them a
> pull request after that.

As my tree currently contains a large proportion of the consolidation work
so far, it probably makes sense for this stuff to continue coming through
my tree so that we can sort out any merge conflicts there, rather than
starting on a new tree... It probably makes sense for the subarch tree to
get going after this merge window has closed.
--
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/