From: tony@atomide.com
To: linux-omap-open-source@linux.omap.com
Subject: Checklist for submitting omap patches
Date: Fri, 28 Apr 2006 01:48:03 -0700 [thread overview]
Message-ID: <20060428084803.GF31797@atomide.com> (raw)
Hi all,
Following a short checklist for submitting omap patches. I've
also posted it to:
http://www.muru.com/linux/omap/README_OMAP_PATCHES
Does anybody have comments or something that should be added?
Regards,
Tony
Submitting OMAP patches version 20060428
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 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
reply other threads:[~2006-04-28 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060428084803.GF31797@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox