Lines Matching full:upstream
3 1. BEST: Make all of your changes to upstream Linux. If appropriate, backport to the stable release…
5 in upstream Linux, post a backport of the patch that conforms to the patch requirements below.
6 …- Do not send patches upstream that contain only symbol exports. To be considered for upstream Lin…
9 - When sending patches upstream, the commit message must contain a clear case for why the patch
13 2. LESS GOOD: Develop your patches out-of-tree (from an upstream Linux point-of-view). Unless these…
23 - If the patch is not merged from an upstream branch, the subject must be tagged with the type of p…
24 `UPSTREAM:`, `BACKPORT:`, `FROMGIT:`, `FROMLIST:`, or `ANDROID:`.
31 ## Requirements for backports from mainline Linux: `UPSTREAM:`, `BACKPORT:`
34 - tag the patch subject with `UPSTREAM:`.
35 - add upstream commit information with a `(cherry picked from commit ...)` line
37 - if the upstream commit message is
39 important patch from upstream
47 UPSTREAM: important patch from upstream
59 - If the patch requires any changes from the upstream version, tag the patch with `BACKPORT:`
60 instead of `UPSTREAM:`.
61 - use the same tags as `UPSTREAM:`
65 BACKPORT: important patch from upstream
80 - If the patch has been merged into an upstream maintainer tree, but has not yet
89 important patch from upstream
97 FROMGIT: important patch from upstream
119 FROMLIST: important patch from upstream