Nit: it's stable_kernel_rules.txt. We should start this way and augment/adjust rules after discussions as we find potential conflicts. Sounds reasonable to me in general. Jan -- Siemens

Ack. Not sure how to read these threads as I didn't manage to follow their evolution: This aspect of support constraints is still in scope? I think it will be important in order to keep backporting

Hi, At LinuxCon EU, during the CIP talk it was announced that the first CIP kernel will be 4.4 Please find the slides of all the 2016 talks about CIP in our wiki[1]. [1]

Hi, the slides[1] from the talk "Long-Term Maintenance, or how to (mis-)manage embedded systems for 10+ years" by Jan Luebbe are available. I assume by next week we will have the video. [1]

The first version is what I wrote, and the correction says something I did not mean to say. No, you understand me rightly. Ben. -- Ben Hutchings Software Developer, Codethink Ltd.

Hi Koguchi-san, I think you are right. It's my fault, sorry. Daniel

Hi Agustin, Let me understand what you wrote. Is the correction correct? I thought you wrote; * Upstream fixes frequently change the kernel module API and/or ABI and backporting them in a way that

Hi, I think it is already there. Sent from mobile. Please excuse my brevity. -- Agustín Benito Bethencourt @toscalix

Hi Agustin, Here are some links for CIP presentations. Probably the following information is also a candidate contents for CIP wiki. * Towards Sustainable Systems with the Civil Infrastructure

Just a remark, the presentation is tomorrow, 10/6 -- Urs Gleim | Siemens AG | Corporate Technology

Hi, CIP ha set up a public wiki. It has very little content at this point and there is no policy yet to add editors. We are sorting things

Hi Agustin, Sorry for the late reply. I think that one possible guideline for backporting security patches to the CIP kernel is to look at kernel CVEs [1]. A table (probably only accessible by

Hi, Correction: Upstream fixes frequently change the kernel module API and/or ABI and backporting them in a way that is difficult and risky - CIP users set their own kernel configurations, so

This is a problem for many companies, actually, but I hope we can still encourage people to participate in IRC, mainly because there are so many established FOSS projects and contributors actively

Hi Everyone, #Alternatives to a Mailing List Slack has been taking the business world by storm, however, The free version has some serious limitations on it. So I started looking for Slack

Hi, let me try to sketch one example for typical rail automation products: - development time of a new system: 3-5 years - customer specific adaptions: 2-4 years - initial safety certifications /

Hi, my name is Urs Gleim. I am with Siemens Corporate Technology. I have a history in embedded systems development with all the big proprietary embedded operating systems out

Hi, just a remark: we have some proxy restrictions in the company which result in the fact that IRC is not really practically usable. So our main communication channel

Hi, at CIP we need to have a clear view of what "Support" means in the context of the Super Long Term Support kernel. ++ What kind of support will CIP provide? To whom? CIP will support its members

Hi, the below considerations were discussed during the Members meeting. There is no conclusion yet about how to proceed. ++ Security fixes +++ Out-of-tree drivers The embedded systems that CIP