From aaac65a46dc97ca3aa52c1d208e86a569dba2673 Mon Sep 17 00:00:00 2001 From: Mark Brown Date: Wed, 15 Jun 2016 11:45:23 +0100 Subject: [PATCH] Update Kernel-Roadmap.md --- Reference-Platform/Kernel-Roadmap.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/Reference-Platform/Kernel-Roadmap.md b/Reference-Platform/Kernel-Roadmap.md index 849ba2c..e0bb2c5 100644 --- a/Reference-Platform/Kernel-Roadmap.md +++ b/Reference-Platform/Kernel-Roadmap.md @@ -1,15 +1,10 @@ ## Introduction -The Reference Platform Kernel(RPK) brings together WIP code that is still under review upstream to provide a single kernel image for 96boards and other Linaro member hardware of interest. +The Reference Platform Kernel (RPK) brings together WIP code that is still under review upstream in case that is useful. The kernel tree is managed similar to linux-next, in that topic branches adding support for various platforms and new kernel features are merged on top of a (close-to-mainline) vanilla kernel. These topic branches are provided by the relevant segment group, Landing Team or vendor engineers who want to add support for a hardware platform or a new feature into RPK. Please review the [[patch-acceptance policy|RP-Kernel-Policy]] for RPK. It is implicit that the person responsible for the feature/platform suppport will rebase it to the new kernel version if that feature is not to be dropped in subsequent kernel releases. See the [table](#kernel-version-table) below for a roadmap of proposed kernel versions for future releases. -## Why is RPK needed? - 1. To allow engineers to focus on new features instead of spending time on HW enablement - 1. To speed up finding integration problems while working upstream - 1. To make it easy to measure the delta between an upstream kernel and what is needed to make a platform useful - ## Kernel Version Table | RPB Release | Kernel Version | LEG | LHG | LNG | LMG | |---|---|---|---|---|---|