- use Linus tree (most prefer)
- sparse check
make C=1 (check compiled files)
make C=2 (check all files)
- git format-patch -s -n --subject-prefix="PATCH v3" -o XXX commitA..commitB
- scripts/checkpatch.pl XXX/*
- 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
- select lists/maintainers to send to.
- Send to yourself first. If no problem, send to all then.
git send-email --to A --to B XXX
arm-linux: Mailing Lists - FAQ
Guide to ARMLinux: Making your own patches
TI Davinci: Patch upstream sending
Re: [GIT PULL] generic arm for MSM
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.
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.