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: <alpine.DEB.2.00.1103310843530.29543@asgard.lang.hm>
Date:	Thu, 31 Mar 2011 08:45:54 -0700 (PDT)
From:	david@...g.hm
To:	Russell King - ARM Linux <linux@....linux.org.uk>
cc:	Thomas Gleixner <tglx@...utronix.de>,
	Kevin Hilman <khilman@...com>, Ingo Molnar <mingo@...e.hu>,
	Nicolas Pitre <nico@...xnic.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	Tony Lindgren <tony@...mide.com>,
	David Brown <davidb@...eaurora.org>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
	Catalin Marinas <catalin.marinas@....com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window

On Thu, 31 Mar 2011, Russell King - ARM Linux wrote:

> 
> On Thu, Mar 31, 2011 at 05:01:40PM +0200, Thomas Gleixner wrote:
>> On Thu, 31 Mar 2011, Kevin Hilman wrote:
>>
>>> Thomas Gleixner <tglx@...utronix.de> writes:
>>
>>> Yes, ARM SoC maintainers have to make up some ground.  But compare this
>>> to just a couple years ago where the common complaint was "why aren't
>>> embedded SoC people contributing code to mainline", and you'll see we
>>> have come a long way.
>>
>> Well, code comes in, which is progress. But we need to figure out how
>> to deal with the increasingly growing flood before we drown in it.
>
> How about we declare the remainder of this cycle and the next merge window
> as being only for bug and regression fixes, and consolidation of stuff like
> the IRQ controller and GPIO controller code for the next merge window?

well, now that -rc1 has been released, the remainder of this cycleis 
already only bug and regression fixes.

declaring the next merge window as the same may or may not help, depending 
on if it pushes people to do more consolodations work or just delay 
submitting the work they are doing.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ