linux-kernel - Re: Protocol for merging -omap changes

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, 27 Oct 2006 18:54:10 +0300
From:	Tony Lindgren <tony@...mide.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Russell King <rmk@....linux.org.uk>,
	kernel list <linux-kernel@...r.kernel.org>, vovan888@...il.com
Subject: Re: Protocol for merging -omap changes

Hi,

* Pavel Machek <pavel@....cz> [061027 15:43]:
> Hi!
> 
> I see that linux-omap still has pretty big difference from
> linux-arm... are there any plans at merging them? Is there some way I
> could help?

Yeah, let's get more of the commonly used omap drivers merged!
 
> I have bunch of siemens sx1 changes from Vladimir here, and some of
> them seem ready to merge... should they be merged with Tony? Or
> directly with rmk bringing stuff from -omap tree as needed?

Core omap stuff goes first to linux-omap tree, and then gets merged
to mainline kernel through RMK. Drivers should go through the
appropriate driver maintainers or LKML.

So please split your patches accordingly. All arch/arm/*omap* and
include/asm-arm/arch-omap patches should be separate from drivers.

Regards,

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