Hi, As I know, we agreed we'll use LTS or LTSi version for the tizen reference kernel version[1]. Please note we can use not only LTSi but LTS kernel. We'll use LTS kernel in mobile profile.
BTW, to merge memfd and kdbus feature, should we wait until next merge windows of LTSi? I think it's really slow development process. I think LTSi kernel will be good we've done the development. During we develop the platform, we would better to accept a new feature after we examine it thoroughly. If it is impossible to accept the new feature on the stable kernel until we've got any review from LTSi, how do we consider landing experimental kernel for the new feature? [1] https://wiki.tizen.org/wiki/Standard_of_Tizen_Reference_Kernel_Version Best Regards, Chanho Park > -----Original Message----- > From: Dominig ar Foll [mailto:[email protected]] > Sent: Thursday, December 04, 2014 10:52 PM > To: Chanho Park; [email protected] > Subject: Re: [Dev] Merging memfd for kernel-common > > Chanho, > > the agreement between Intel and Samsung was that Tizen 3 Common would be > based on LTSI 3.14. > You are right his is LTSI and not LTS. > > LTSI accept patches from the LTS (while still alive) and from the > industry and has a longer maintenance period than a simple LTS. > > As 3.14 was promoted to LTSI very recently (during Linux Con Düsseldorf > in Oct 14), today LTSI and LTS are still the same, but that will not > continue. > > If you get your patch in LTSI 3.14, you will arrive in Common > automatically :-) > > If not you have to get the agreement that at least two profiles are > requesting the feature to get in Common. > > Last option, will be to keep the patch in the only profile that requires > it :-( > > Regards > > Dominig > > > Le 04/12/2014 14:40, Chanho Park a écrit : > > Hi Dominiq, > > > > Longterm > > There are usually several "longterm maintenance" kernel releases > > provided for the purposes of backporting bugfixes for older kernel > trees. > > Only important bugfixes are applied to such kernels and they don't > usually > > see very frequent releases, especially for older trees.[1] > > > > You mean we only focus on LTSi kernel not LTS, right? If so, we should > sync > > with LTSi kernel not LTS. > > The first merge windows of the LTSi-3.14.24-rc1 was closed in October. > There > > is only four patches top of the 3.14.24 :( > > > > [1]: https://www.kernel.org/category/releases.html > > > > Best Regards, > > Chanho Park > > > >> -----Original Message----- > >> From: Dominig ar Foll [mailto:[email protected]] > >> Sent: Thursday, December 04, 2014 10:01 PM > >> To: Chanho Park; [email protected] > >> Subject: Re: [Dev] Merging memfd for kernel-common > >> > >> Chanho, > >> > >> no as part of the LTSI initiative you can add some feature from > backport > >> when it makes sense. > >> I do not know if they would accept it, but as we are aligned on LTSI > and > >> we will need to keep fetching their minor releases to get security > bug > >> correction, it's very important to get an alignment there. > >> > >> Having to carry a patch for ever, is not an attractive solution and > >> woudl be difficult to justify for Tizen Common. > >> > >> Regards > >> > >> Dominig > >> > >> Le 04/12/2014 13:54, Chanho Park a écrit : > >>> Hi, > >>> > >>>> -----Original Message----- > >>>> From: Dev [mailto:[email protected]] On Behalf Of Dominig > >> ar > >>>> Foll > >>>> Sent: Thursday, December 04, 2014 9:49 PM > >>>> To: [email protected] > >>>> Subject: Re: [Dev] Merging memfd for kernel-common > >>>> > >>>> Hello, > >>>> > >>>> could you please submit your patch to LTS/LTSI 3.14 as well and > >> report > >>>> success or rejection. > >>> Actually, it is impossible we add a new feature into stable kernel. > >> The > >>> memfd is the new feature of 3.17 kernel. > >>> Only stable patch will be acceptable in stable tree. > >>> > >>> Best Regards, > >>> Chanho Park > >>> > >>>> Thanks > >>>> > >>>> Dominig > >>>> > >>>> Le 04/12/2014 11:51, Maciej Wereski a écrit : > >>>>> Dear kernel-common maintainers, > >>>>> > >>>>> A week ago I've send set of backported patches (from 3.17), that > add > >>>> and > >>>>> wire memfd. This is new feature and it shouldn't break anything. > It > >> is > >>>>> requirement for kdbus and kdbus will become systemd requirement > when > >>>>> it is > >>>>> merged. Could you please review these and hopefully merge? > >>>>> > >>>>> kind regards, > >>>> -- > >>>> Dominig ar Foll > >>>> Senior Software Architect > >>>> Intel Open Source Technology Centre > >>>> > >>>> _______________________________________________ > >>>> Dev mailing list > >>>> [email protected] > >>>> https://lists.tizen.org/listinfo/dev > >> -- > >> Dominig ar Foll > >> Senior Software Architect > >> Intel Open Source Technology Centre > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
