Sending patches

Jump to: navigation, search

We currently use the Mailing list as a code review and integration tool, feel free to send your patches using git send-email.


Patches for New Devices

Patches going upstream (mainline) are managed on other mailing lists and by their particular maintainers. You need not subscribe to these list for sending patches. To ensure your patches integrate well, use the following repositories. Find information how to actually make the modifications in the section linked in the Topic column.

Topic Repository to patch against Patch receiver(s) Example
Fex [1]
u-boot-sunxi (Deprecated!) [2]
mainline u-boot;a=tree;hb=refs/heads/next
[3], [4]
linux-sunxi [5]
mainline kernel (.dts) Use the get_maintainer script as shown below

Patches for Tools and Drivers

The main repositories to clone and base from are all maintained at GitHub ( ) - these include linux kernel sources, u-boot sources, tools and other associated libraries such as MALI 3D graphics and CEDAR Video engine.

Setting up git send-email

  1. Install git-email addon using your favorite package manager
  2. $ git config --global sendemail.smtpserver
  3. $ git config --global sendemail.smtpuser yourusernameforsmtp
  4. $ git config --global sendemail.smtppass yourpassword
  5. $ git config --global sendemail.from
  6. $ git config --global sendemail.chainreplyto false

Using git send-email

  1. $ git format-patch -1 longcommithashhere
  2. $ git send-email 0001-whatever-file-it-generated.patch

If you're sending patches to the mainline kernel, you can get a list of the recipients of the patch using:

  1. $ ./scripts/ 0001-whatever-file-it-generated.patch

It will ask you whom to send it to (use and that's it!

More information

Personal tools