Skip to content

Instantly share code, notes, and snippets.

@digetx
Last active September 15, 2025 03:00
Show Gist options
  • Select an option

  • Save digetx/60e2b5e0510395b37ebf3fba96d9a24f to your computer and use it in GitHub Desktop.

Select an option

Save digetx/60e2b5e0510395b37ebf3fba96d9a24f to your computer and use it in GitHub Desktop.
1. You want to upstream these patches:
68e5c4b64765 ASoC: tegra: Add RT5631 machine driver
2bac54936f27 ASoC: dt-bindings: tegra: Add binding for RT5631
2. Create patches
# git format-patch -v1 --cover-letter -2 68e5c4b64765
Now you have these files:
v1-0000-cover-letter.patch
v1-0001-ASoC-dt-bindings-tegra-Add-binding-for-RT5631.patch
v1-0002-ASoC-tegra-Add-RT5631-machine-driver.patch
3. Check patches
# ./scripts/checkpatch.pl --strict v1*
If there are errors and warnings, fix them and go back to 1.
4. Open v1-0000-cover-letter.patch in text editor. Fill the SUBJECT
and give a short description, telling what these patches are doing
and why they are needed.
5. Get a list of email addresses to whom send the patches.
# ./scripts/get_maintainer.pl v1*
You'll get this list:
Liam Girdwood <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
Mark Brown <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...,commit_signer:7/9=78%,commit_signer:6/8=75%)
Rob Herring <[email protected]> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
Thierry Reding <[email protected]> (supporter:TEGRA ARCHITECTURE SUPPORT,in file)
Jonathan Hunter <[email protected]> (supporter:TEGRA ARCHITECTURE SUPPORT,commit_signer:1/8=12%,in file)
Jaroslav Kysela <[email protected]> (maintainer:SOUND)
Takashi Iwai <[email protected]> (maintainer:SOUND)
Sameer Pujar <[email protected]> (commit_signer:6/9=67%,authored:6/9=67%,added_lines:65/82=79%,commit_signer:6/8=75%,authored:6/8=75%,added_lines:12/16=75%)
Sergey Larin <[email protected]> (commit_signer:3/9=33%,commit_signer:3/8=38%)
Svyatoslav <[email protected]> (commit_signer:1/9=11%,authored:1/9=11%,added_lines:8/82=10%,commit_signer:1/8=12%,authored:1/8=12%,added_lines:2/16=12%,commit_signer:1/1=100%,authored:1/1=100%,added_lines:261/261=100%)
Ion Agorria <[email protected]> (commit_signer:1/9=11%,commit_signer:1/1=100%)
"Michał Mirosław" <[email protected]> (authored:1/9=11%,removed_lines:1/1=100%)
ryang <[email protected]> (authored:1/9=11%,added_lines:9/82=11%,authored:1/8=12%,added_lines:2/16=12%)
Stephen Warren <[email protected]> (in file)
[email protected] (moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
[email protected] (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
[email protected] (open list:TEGRA ARCHITECTURE SUPPORT)
[email protected] (open list)
You are interested in maintainers, mailing lists and everyone who are directly related
to the patches. Ignore others. Hence you're interested in:
Liam Girdwood <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
Mark Brown <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...,commit_signer:7/9=78%,commit_signer:6/8=75%)
Rob Herring <[email protected]> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
Thierry Reding <[email protected]> (supporter:TEGRA ARCHITECTURE SUPPORT,in file)
Jonathan Hunter <[email protected]> (supporter:TEGRA ARCHITECTURE SUPPORT,commit_signer:1/8=12%,in file)
Jaroslav Kysela <[email protected]> (maintainer:SOUND)
Takashi Iwai <[email protected]> (maintainer:SOUND)
Svyatoslav <[email protected]> (commit_signer:1/9=11%,authored:1/9=11%,added_lines:8/82=10%,commit_signer:1/8=12%,authored:1/8=12%,added_lines:2/16=12%,commit_signer:1/1=100%,authored:1/1=100%,added_lines:261/261=100%)
Ion Agorria <[email protected]> (commit_signer:1/9=11%,commit_signer:1/1=100%)
Stephen Warren <[email protected]> (in file)
[email protected] (moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
[email protected] (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
[email protected] (open list:TEGRA ARCHITECTURE SUPPORT)
[email protected] (open list)
You may add me to the list since I helped you with the patches.
Dmitry Osipenko <[email protected]>
6. Send patches
I'll use my Gmail for example:
# git send-email --smtp-server=smtp.gmail.com [email protected] --smtp-encryption=tls --smtp-server-port=587 --suppress-cc=all --to 'Thierry Reding <[email protected]>' --to 'Jonathan Hunter <[email protected]>' --to 'Stephen Warren <[email protected]>' --to 'Mark Brown <[email protected]>' --to 'Takashi Iwai <[email protected]>' --to 'Jaroslav Kysela <[email protected]>' --to 'Rob Herring <[email protected]>' --to 'Svyatoslav <[email protected]>' --to 'Ion Agorria <[email protected]>' --to '' --to 'Dmitry Osipenko <[email protected]>' --cc '[email protected]' --cc '[email protected]' --cc '[email protected]' --cc '[email protected]' --confirm=always v1*
Use "--to" for people and "--cc" for mailing lists.
Git will print out list of email recipients and files to send, check that everything looks okay.
Git asks "Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll):", answer "all".
Enter your email password and wait till all patches are sent out by git. Done.
If everything went okay, you'll see your patches in patchwork of the mailing lists:
https://patchwork.ozlabs.org/project/linux-tegra/list/
https://patchwork.kernel.org/project/alsa-devel/list/
7. Wait for review comments. Depending on a maintainer, it may take couple days, a week or more than a month. Be prepared
that you may not get quick replies, just wait. If nobody answered for more than a month or two, go to 1 and send patches
again.
8. If maintainer requsted to make changes, make them and go back to 1. Use "-v2" for `git format-patch ..` to bump version of
the patches to v2.
9. Maintainer will answer you if everything is okay and patches are applied. Done.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment