This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
civilinfrastructureplatform:cipkernelmaintenance [2018/05/28 11:07] Agustin Benito Bethencourt [CIP kernel - SLTS kernel] |
civilinfrastructureplatform:cipkernelmaintenance [2018/10/15 04:38] daniel.sangorrin [Maintenance Scope] add a link to our patchwork site |
||
---|---|---|---|
Line 67: | Line 67: | ||
The embedded systems that CIP will be used in will also often require out-of-tree drivers and will sometimes include other changes of unknown quality to their kernel. These modifications are in general unsupported. If a bug is found in such a modified kernel, Members will first demonstrate that it exists in the CIP source release in order for the CIP maintainers to act on it. | The embedded systems that CIP will be used in will also often require out-of-tree drivers and will sometimes include other changes of unknown quality to their kernel. These modifications are in general unsupported. If a bug is found in such a modified kernel, Members will first demonstrate that it exists in the CIP source release in order for the CIP maintainers to act on it. | ||
- | For specific CIP applied patches, the default communication channel will be the [[https://lists.cip-project.org/mailman/listinfo/cip-dev|CIP-dev]] mailing list. | + | For specific CIP applied patches, the default communication channel will be the [[https://lists.cip-project.org/mailman/listinfo/cip-dev|CIP-dev]] mailing list. Patches sent to the cip-dev mailing list are tracked on [[https://patchwork.kernel.org/project/cip-dev/list/|patchwork]] since October 12nd, 2018. |
+ | |||
+ | [[https://gitlab.com/cip-project/cip-kernel/cip-kernel-config|Kernel configuration files]] provided by Members will be used as a reference to limit the maintenance scope. Here is a list of recommendations related to kernel configuration for long-term support: | ||
+ | * [[https://lists.cip-project.org/pipermail/cip-dev/2017-May/000263.html]] | ||
+ | * [[https://lists.cip-project.org/pipermail/cip-dev/2017-July/000387.html]] | ||
+ | * [[https://lists.cip-project.org/pipermail/cip-dev/2018-October/001578.html]] | ||
==== Security fixes ==== | ==== Security fixes ==== | ||
Line 137: | Line 143: | ||
* If there is already a fix in Linus's git repository, ask for it to be included in a stable update straight away. | * If there is already a fix in Linus's git repository, ask for it to be included in a stable update straight away. | ||
* Otherwise, if the patch that introduces the regression hasn't yet been applied then you should ask for it to be deferred (or never applied, if it was reverted upstream). | * Otherwise, if the patch that introduces the regression hasn't yet been applied then you should ask for it to be deferred (or never applied, if it was reverted upstream). | ||
+ | |||
+ | ==== CIP kernel maintenance status ==== | ||
+ | * [[linux-4.4.y| linux-4.4.y review]] | ||
[[start|Back to the parent page]] | [[start|Back to the parent page]] | ||