These are markdown pages offering some notes about what linux-stable is, how you should be using it, and issue resolution notes.
These are pages dedicated to answering what this stuff is and why it is important. Everyone should read these! If your kernel developer doesn't care for this process after reading this, they don't care about your security or stability...
what-is-linux-stable.mdgives an overview of what linux-stable is and how it came about.why-is-linux-stable-importantgives some reasons why this is important and addresses some of the excuses that people give for not caring about it (when they definitely should).
how-togoes over the proper process for adding the latest linux-stable into your kernel.tips-and-tricks.mdcontains a few pointers and hints regarding this process.
These are notes for developers to help with merging linux-stable into their own repos by documenting all of the conflicts, where they come from, and what was done to solve them. These repos are up to date with the latest linux-stable along with the latest commits from their OEMs.
-
msm-4.4-conflict-resolution.mdfor the msm-4.4-linux-stable repository (stock CAF source, based on the LA.UM.6.4.r1-04900-8x98.0 tag). -
op5-conflict-resolution.mdfor the op5-linux-stable repository (stock OP5 source, based on the OOS Open Beta 1 branch). -
wahoo-conflict-resolution.mdfor the wahoo-linux-stable repository (stock Pixel 2 and Pixel 2 source, based on the (android-8.0.0_r0.28 tag).
These kernels do not contain everything needed to boot and use the device as normal in their current form. Since these kernels are designed to be used as a base for others or merged into existing working kernels, those commits will not be added. Instead, I give notes that can be used to get everything working properly.
wahoo-usability.mdfor using the Pixel 2 and Pixel 2 XL kernel sourceop5-usability.mdfor using the OnePlus 5 kernel source
Should you chose to merge, use the following commands:
git fetch <repo_url> <branch>
git merge FETCH_HEADShould you chose to use the kernel as a base for your own, either fork the kernel or run the following in an existing kernel repo:
git fetch <repo_url> <branch>
git branch -b <branch_name> FETCH_HEAD
git push --set-upstream origin <branch_name>This will keep commit history and make it easier to keep up with updates. You can either merge the updates from this tree by using the merge commands above or add linux stable as a remote and merge changes from there:
git remote add linux-stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
git fetch linux-stable
git merge v<version>Do not ask me permission to use these, they are freely available for a reason. Additionally, you don't need to give me credit for any public releases you do (although it would be appreciated). I'm not in this for glory, I just want people to be more stable and secure. Enjoy!