[meta-ti] process for security kernel patches

[Sona Sarmadi]

Dear Denys, all,

Can you please inform us what is your process for getting security kernel patches for linux-keystone used in the meta-ti layer (poky/meta-ti/recipes-kernel/linux/linux-keystone_3.10.bb)? 

Do you  track the -stable updates? Is there a process in place to get security related fixes into the meta-ti kernels (e.g. linux-keystone_3.10)?

We have in the past sent some security patches to meta-ti at yoctoproject.org list but haven't got any response so far:
Here are some patches:
https://lists.yoctoproject.org/pipermail/meta-ti/2014-August/004980.html
https://lists.yoctoproject.org/pipermail/meta-ti/2014-April/004360.html

We have some more security patches ready for upstream but we are not sure what your policy is? Can we send these patches as well and wait for them to get reviewed and merged or should we stop sending the kernel security patches to "meta-ti at yoctoproject.org" list? Maybe we should upstream in different way? To another list?

We can of course apply these patches in our own layer (meta-enea) but we want to fix in the meta-ti layer and contribute to the Yocto/community (other meta-ti/ linux-keystone users). 

BR - Sona

Sona Sarmadi
Software Engineer/Security Responsible for Enea Linux
Enea
Jan Stenbecks torg 17,
Box 1033, SE-164 21 Kista, Sweden
Direct: +46 8 5071  4475
Mobile: +46 70 971 4475
sona.sarmadi at enea.com
www.enea.com 



This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone.