Sending patch to community

1. use Linus tree (most prefer)
2. sparse check
   make C=1 (check compiled files)
   make C=2 (check all files)
   
3. git format-patch -s -n --subject-prefix="PATCH v3" -o XXX commitA..commitB
4. scripts/checkpatch.pl XXX/*
   
5. write a brief [PATCH v3 0/X] XX (copy a patch content, and modified it as 0/XX), add result of following command to the end of the file. Add the based linux tree (e.g. linux-2.6.37-rc2)

   git shortlog commitA..commitB
   git diff --stat --summary commitA..commitB

6. select lists/maintainers to send to.
7. Send to yourself first. If no problem, send to all then.

   git send-email --to A --to B XXX

---

arm-linux: Mailing Lists - FAQ
http://www.arm.linux.org.uk/mailinglists/faq.php

Patch State
http://www.arm.linux.org.uk/developer/patches/

Guide to ARMLinux: Making your own patches
http://www.aleph1.co.uk/oldsite/armlinux/book/x1699.html

TI Davinci: Patch upstream sending
http://processors.wiki.ti.com/index.php/Patch_upstream_sending

Re: [GIT PULL] generic arm for MSM
http://www.spinics.net/lists/arm-kernel/msg85062.html

Never base your tree on linux-next. You really should use a stable tree, such as Linus' tree. The linux-next tree is constantly thrown away and rebuilt, and your own tree will keep a reference on that obsoleted linux-next version otherwise.

http://www.spinics.net/lists/arm-kernel/msg85110.html

As people have said you should *never* send any pull requests based on-next, it's a constantly rebasing merge of various development trees ofvarying quality and so will never be merged into mainline. If you aresending stuff based on -next for some reason send it as a patches.

Documentation/sparse.txt
http://www.mjmwired.net/kernel/Documentation/sparse.txt