How to submit a patch to OpenEmbedded

Revision as of 09:23, 2 September 2022 by Michael Opdenacker (talk | contribs) (A task-oriented guide to creating a patch: Improve git-send-email documentation. Mention the sometimes important sendemail.from git setting.)
Jump to: navigation, search

OpenEmbedded welcomes contributions. Before submitting a patch however there are a few things to keep in mind.

Finding the right place for your patch

OpenEmbedded is now split up into separate layers: OpenEmbedded-Core (OE-Core) which is a small set of core recipes, and other layers for recipes beyond that. For most layers, patches are sent to a mailing list for review before being merged. For further information specific to the layer you're working on, please see the README file in the layer.

New recipes in particular should be added to the appropriate layer. See the layer index for the list of public layers. If your new recipe doesn't seem to fit anywhere it can be added to the meta-oe layer in the meta-openembedded repository, although if it is likely to be followed by numbers of similar recipes then you may wish to consider creating a new layer.

A task-oriented guide to creating a patch

Let's say you have made a fix to a recipe, you've tested that it works and you'd like to submit it for merging.

Set up git

Properly configuring git (using as an example user)

On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)

sudo aptitude install git-core git-email

These are important to the commit meta-data

git config --global "Ada Lovelace"
git config --global ""

Subscribe to the mailing list

You need to subscribe to the appropriate mailing-list in order to be able to send your patch(es) there; for patches against OE-Core the mailing list is and for patches against meta-oe and many other layers the list is See Mailing lists for subscription and further details.

Committing your patch

Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code.

cd oe-core/ # or whereever you keep your clone of the repo
git add meta/recipes-devtools/flex
git commit -s # don't use the -m option but include my signature
   flex: backport Debian patches to fix generated code warnings
   The generated parser had warnings regarding signess and return check
   which makes Linux Kernel's perf tool from 3.4 release to fail without
   those patches.

All commit messages must include Signed-off-by (-s option to commit as above). For more guidelines on messages please see Commit Patch Message Guidelines.

Note that when adding multiple new recipes, each recipe should be added in a separate commit. For upgrades of existing recipes, the previous version should usually be deleted as part of the same commit to add the upgraded version.

Sending patches

There are two possible methods for submitting patches. Either one is acceptable; for a series containing a number of patches the pull request method is preferred although not mandatory.

Sending using git-send-email

The following will ensure that your e-mails have a correct From field. This field is used by git am to recreate commits with the right author name.

git config --global sendemail.from ""

Here are settings for sending your e-mails through Google Mail's SMTP server:

git config --global sendemail.smtpserver
git config --global sendemail.smtpserverport 587
git config --global sendemail.smtpencryption tls
git config --global sendemail.smtpuser

You can use git send-email's --envelope-sender option to have the email appear from the address you are subscribed to the list with. You will need to use the Accounts and import tab under the Gmail settings tab. Use the Send mail as selection to address you want to send email from.

To send just the top commit on your current branch (substitute mailing list address as appropriate):

git send-email --confirm=always -M -1

For multiple commits you can substitute -1 above with -N (where N is the number of commits) or instead specify a revision before which to start e.g. HEAD~3, master etc.

Note: in either case if you are submitting a patch for meta-oe or any layer other than OE-Core, please add the appropriate prefix so that it is clear which layer the patch is intended to be applied to:


Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

Sending via a pull request

Alternatively, for larger patch series it is preferable to send a pull request which not only includes the patch but also a pointer to a branch that can be pulled from. This involves making a local branch for your changes, pushing this branch to an accessible repository and then using the create-pull-request and send-pull-request scripts (supplied with OE-Core) to create and send a patch series with a link to the branch for review. Step-by-step instructions:

  1. Find a repository to push your changes to, and add this as a remote to your git working tree. If you're going to be submitting a lot of changes, some of the repositories have a corresponding -contrib repository which you can use for this purpose - access to these for OE-related work is open to anyone who requests it. Otherwise github or some other public git hosting service can suffice.
  2. Create a branch for your changes if you haven't already. Other than backports from master or fixing bugs that only occur in an older branch, this should be on top of the master branch.
  3. Push the branch to the remote.
  4. Run scripts/create-pull-request -u remote-name (where remote-name is the name of the remote where you'll be pushing the branch). For meta-oe and other layers where a single mailing list covers more than one layer you'll need to add -p "layername][PATCH" replacing layername with the name of the layer so that it is clear which layer the patches are intended for.
  5. The script will report that it has created a pull-XXXXX directory has been created. Edit the pull-XXXXX/0000-cover-letter.patch with your favourite text editor and change the title and top of the body as appropriate.
  6. Run scripts/send-pull-request -p pull-XXXXX -t (replacing with the appropriate mailing list address for layers other than OE-Core). Where there is a clear maintainer for the area you're changing it may also help to add -C
Request OE contrib Write Access

please send an email to Michael Halstead and:

  1. Attach your ssh public key which usually named If you don't have one generate it by running ssh-keygen -t rsa -b 4096 -C "".
  2. List the repositories you're planning to contribute to.
  3. Include your preferred branch prefix for *-contrib repositories.

Backporting fixes to stable releases

When a bug is present on a stable branch of OE yet has been fixed in master one can request that the stable branch's maintainer accept the fix into the stable branch. The best way to do this is generate a patch with the backport and submit it to the mailing list (CC'ing the maintainer may help the patch be reviewed for inclusion more quickly).

Patches for stable branches should be prefixed with the branch name (which is the same as the release series name), for example morty, pyro, etc. Once you've identified the commit hash of the patch you'd like to see accepted as a backport you can generate the patch with:

git format-patch <COMMIT_HASH> -1 --subject-prefix="<BRANCH_NAME>][PATCH"

The generated patch can then be sent using the procedure described above.

Community review

Your patch will be sent to the mailing list and for some layers should be immediately visible on

If you get feedback in reply to your patch, you should make changes according to the feedback and submit the next version. Please remember to use --subject-prefix="PATCH v2", v3, v4 etc. to mark the patch iteration. Please also test your revised changes - in particular don't just edit the patch file written out by git-format-patch and resend it.

If your patch has not had any feedback after a few days it may have been missed or the appropriate reviewers may not currently be around; it is perfectly fine to reply to it yourself with a "ping" / reminder request for feedback. NOTE: patch review for feature / recipe upgrade patches will likely be delayed during a feature freeze because these types of patches aren't merged during this time - you may have to wait until after the freeze is lifted.


Steps for people which don't have SMTP access for git

Patches should not be sent as attachment but inline.

If you do not have SMTP access to your email account you have two options:

1. Use a different account (e.g. gmail). you can make one especially for this. Note that the account may differ from the one in signed-off (although that is inconvenient)

2. Just include the patch in the body of your email. Make sure you use an email client that does not touch the message (turn spaces in tabs, wrap lines etc etc).

A good mail client to do so is pine (or alpine) or mutt. For more information refer to Documentation/email-clients.txt in linux kernel sources.

Streamlining git-send-email with configuration

Don't want to have to remember to specify the right options when using git-send-email (or the pull request script)? You can actually set these in git's configuration and save yourself a lot of hassle.

  • Always confirm sending (for all repositories):
    git config --global sendemail.confirm always
  • Set send-to email address for the repository (don't forget to specify the right address!):
    git config --local
  • If the mailing list requires a subject prefix for the layer (only works when the repository only contains one layer; set layer name as appropriate):
    git config --local format.subjectprefix "meta-something][PATCH"

See also