> -----Original Message----- > From: Dev [mailto:[email protected]] On Behalf Of Maciej Wereski > Sent: Tuesday, December 09, 2014 8:23 AM > To: [email protected]; Dominig ar Foll > Subject: Re: [Dev] Merging memfd for kernel-common > > Dnia czwartek, 4 grudnia 2014 13:49:22 Dominig ar Foll pisze: > > Hello, > > > > could you please submit your patch to LTS/LTSI 3.14 as well and report > > success or rejection. > > As I've written I'll try to submit memfd also for LTSI. I've got 1 question > though. I've seen that there are many patches (mostly SMACK) on top of > both > kernel-common and linux-stable. Were these submitted to LTSI?
Some of the Smack patches introduce features, so they are not appropriate for LTSI. > Nevertheless I'd like to ask for merging these patches anyway. Even if LTSI > won't accept memfd, we will have to backport them. If LTSI accepts memfd, > memfd commits on Tizen kernels can be easily dropped. > > Merging these now means also that backport will be better tested. We're > working on images with kdbus and less differences between kdbus and stock > images means less problems in the future with integrating kdbus. > > Currently we've tested kdbus with kernel-common+memfd on x86_64 and > qemu-arm > and there were no problems with memfd. > > We'll do one change though, drop memfd on kernel-common and submit is > on > linux-stable (as Patrick suggested, thanks). After that we kindly ask to merge > memfd regardless of memfd in LTSI status. > > By the way, how should linux-base be tested? According to [1] linux-stable > isn't build, only kernels that base on it. Is testing kernel-common > sufficient? > If it is, then tomorrow I'm going to move memfd patches to linux-stable for > review. > > [1] <https://wiki.tizen.org/wiki/File:Tizen_Kernel_Inheritance_Model.png> > > > 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, > > regards, > -- > Maciej Wereski > Samsung R&D Institute Poland > Samsung Electronics > [email protected] > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
