summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 7ac7abf)
raw | patch | inline | side by side (parent: 7ac7abf)
author | Dan Murphy <dmurphy@ti.com> | |
Thu, 3 Sep 2020 14:07:29 +0000 (09:07 -0500) | ||
committer | Dan Murphy <dmurphy@ti.com> | |
Thu, 3 Sep 2020 14:07:29 +0000 (09:07 -0500) |
Add documentation to the README to clarify what the ti-linux branch is
for and when to submit patches.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
for and when to submit patches.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
README.md | patch | blob | history |
diff --git a/README.md b/README.md
index 2cf4277e59dd703ae49dc6364be70cce75bccbe6..754c8b666a225196f5f19f07def6ce29c0dfc676 100644 (file)
--- a/README.md
+++ b/README.md
When Linus tags a new kernel version, a branch will be created for that kernel version, e.g. `linux-5.7.y`. If stable releases for that kernel version will cause breakage with DT or configs, which is unlikely but possible, the patches can be added to `linux-5.7.y` to make it work with latest stable of that version.
+`ti-linux-x.y.z` branch is the development branch that works with the TI productized `ti-linux-x.y.z` kernel branch. When the kernel ti-linux branch is tagged this repo and branch will be tagged with the corresponding tag.
+
+Patches to the overlays should always be submitted to the `master` branch and if applicable back ported to the `ti-linux-x.y.z` branch. Only patches that are applicable to the `ti-linux-x.y.z` features should be submitted to that branch.
+
## DT Overlays
The makefile does two things: