Apologies, the following item was missed out of the report: * build artifacts - we're still unable to retrieve these and get 404 errors on selecting the link:

* Virtual machine creation for the testing We've created 2 vagrant instances one for kernelci and the other for lava (lava is Debian based and kernelci is ubuntu based) work is in progress on

Hi, It does, thanks. I sent Dmitry Shmidt a mail this morning asking for this. Thanks. -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi! The Android common kernel tree is visible here: https://android.googlesource.com/kernel/common/ In the android-4.4 branch, the backport are these: b471fcd FROMLIST: mm: ASLR: use

Hi, Please do so. -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi, in the previous CIP Members meeting a question was made related with the 4.4 LTS kernel EOL (end of life). I have added to the wiki basic links that answers this question. Link:

[Sorry for the delay; I haven't been feeling well.] I would normally cc the upstream developers, but I was hesitant to do so for CIP because this is not related to an official stable branch. Perhaps

As before we're including outstanding problems as gitlab issues - read them for more information! CIP - build artifacts - we're still unable to retrieve these. We have manually

I've chatted with Elena over this last week, and she talked to Kees who pointed out that the Android people are also doing KSPP backports to 4.4 (thanks, folks!). I didn't check any details, just a

CIP developer update, we're including outstanding problems as gitlab issues and there's more information at the issue links. CIP - On retrieving build artifacts - we still have issues here.

Hi, this is an overview of what is happening at CIP. Feel free to answer this mail with your bits. ++ Meetings * Members meeting on Mon Nov 28th ** The next f2f meeting will take place at ELC in

Did you try to discuss the back-port topic with the KSPP folks or other key persons involved in these patches? In the ideal case, the authors can be CC'ed, do not get annoyed by "these crazy people

From: David Decotigny <decot@...> commit 5038056e6bd45788235e97e3bcfc43f96c52ca84 upstream. This also can address following UBSAN warnings: [ 36.640343]

From: Eric Dumazet <edumazet@...> commit adb03115f4590baa280ddc440a8eff08a6be0cb7 upstream. Jiri Pirko reported an UBSAN warning happening in ip_idents_reserve() [] UBSAN: Undefined

From: Xie XiuQi <xiexiuqi@...> commit 79c350e45ebc5a718cc2d7114b45ad560069423d upstream. Use 1U for unsigned int to avoid a overflow warning from UBSAN. [ 31.910858] UBSAN: Undefined

From: Xie XiuQi <xiexiuqi@...> commit ae0119f5f73b1e9cf7177fbbeea68d74c5751def upstream. Use 1UL for unsigned long, or we'll meet a overflow issue with UBSAN. [ 15.589489] UBSAN: Undefined

From: Seung-Woo Kim <sw0312.kim@...> commit 04d68dea26b0a409d44e87ea573a131b6dc67e78 upstream. From pwm_samsung_calc_tin(), there is routine to find the lowest divider possible to generate

From: Vegard Nossum <vegard.nossum@...> commit 979515c5645830465739254abc1b1648ada41518 upstream. I ran into this:

From: Vegard Nossum <vegard.nossum@...> commit 12311959ecf8a3a64676c01b62ce67a0c5f0fd49 upstream. I got this:

From: Nicolas Iooss <nicolas.iooss_linux@...> commit 901d805c33fc4c029fc6b2d94ee5fb7d30278045 upstream. handle_object_size_mismatch() used %pk to format a kernel pointer with pr_err(). This