Submitting OMAP patches version 20080118 As linux-omap tree is almost in sync with the mainline kernel, all core omap patches need to in suitable format for sending upstream. The reason for this is to produce a clean revision history, make maintenance easier, and give proper credit to the patch author. The core omap patches include anything that touches the following directories: arch/arm/plat-omap arch/arm/mach-omap1 arch/arm/mach-omap2 include/asm-arm/arch-omap Anything else is considered non-core omap code, and must be in separate patches. When submitting a patch, please check the following: - Patch follows linux/Documentation/CodingStyle - Patch follows linux/Documentation/SubmittingPatches - Patch does not cause warnings when checked with scripts/checkpatch.pl - Patch does not use double except in comments. Please use tabs or single space instead. Upstream merge tools check for these, so they will cause potentially differerent patch be applied to linux-omap compared to mainline - Patch subject must be [PATCH] ARM: OMAP: Subject of the patch - Patch body must contain short description of the patch - Patch body must contain proper Signed-off-by: line - Non-core patches are in separate patches - Driver patches should be posted to the associated mailing list or LKML and will get merged by the driver maintainers