So if you want your patch to be applied to mainline kernel, you need to send it to kernel mailing lists for review first. You can see a lot of merge commits from him in git log.
#Github linux kernel code#
You need to understand merging policy: only Linus can actually merge code to the mainline tree. Actually there are many of them, they are called maintainers trees. Adventurous testers are very welcome to runtime-test the -next kernel. This way, the -next kernel gives a summary outlook onto what will be expected to go into the mainline kernel at the next merge period. For this purpose, a special testing repository exists into which virtually all subsystem trees are pulled on an almost daily basis: Here is the description from kernel process documentation:īefore updates from subsystem trees are merged into the mainline 4.x tree, they need to be integration-tested. It also should be mentioned that there is linux-next tree. In this case branches are needed because developers have to backport some bug fixes into released versions. Some of those branches are LTS kernels (read this for details). Whenever you see y suffix - it's a stable kernel branch. Where y suffix is just a placeholder for a bugfix version (because naming scheme is linux-4.x.y). In this tree you should look for branches (rather than tags): $ git branch -a "Stable" means that after release, some bug fixes would be back-ported to it. So Linus sticks to tags (instead of branches) in this case. There is no need in a bunch of branches for mainline kernel, as development process in this tree never stops, and once new version is released, there won't be any back-porting to that version (inside mainline tree). You can checkout to desired tag like that: $ git checkout v4.0 This command will show you all version tags: $ git tag Although it has only master branch, you can checkout to any kernel version using tags. It's called mainline kernel, which means this tree is the one where actual development of next kernel version is happening. You probably want to use Linus Torvalds' tree, which is torvalds/linux.git. First of all: don't use that github link (it's just a mirror).
0 kommentar(er)
