I compared this to the upstream version (commit 34e8d993a68ae459ad98c27afc07647e439deacc) and I roughly understand why the clocks are described differently, but can you explain why there's no soc

I've released Linux version 4.4.83-cip8. This adds some backported Renesas platform support plus the fixes from stable versions 4.4.76-4.4.83 inclusive. (I also tagged a version 4.4.75-cip7 which

Hi, Ah, this is already ongoing. Best Regards -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi, (Apologies if yo receive this mail twice, I have experienced some technical issues.) in the previous TSC bi-weekly call there were two To-dos in the kernel maintenance section I would like to

Hi, apologies for sending the mail several times. There was an issue with my mail server. I thought I cancel the request for moderation of at least one of the copies though. -- Agustin Benito

Agustin Benito Bethencourt <agustin.benito@...> writes: <snip> #129 is also associated with this but for the moment leaving it open hoping for feedback from the reporter This just needs

Hi all, these are the main tasks done in the areas where Codethink is focusing the effort the past three weeks (Weeks 31 to 33) ++Kernel maintenance * The review of the LTS patches to update a CIP

Hi all, these are the main tasks done in the areas where Codethink is focusing the effort the past three weeks (Weeks 31 to 33) ++Kernel maintenance * The review of the LTS patches to update a CIP

Hi all, these are the main tasks done in the areas where Codethink is focusing the effort the past three weeks (Weeks 31 to 33) ++Kernel maintenance * The review of the LTS patches to update a CIP

Hello Ben and folks, Let me clarify the level of support. I think there are multiple support levels: (1) Backporting security fix (2) Backporting other bug fix (3) Backporting additional

You need to add the upstream commit hashes to the commit messages, like in stable backports. I think this is fine so long as both drivers (8250_pci and 8250_exar) are tested. This includes API

I don't see backporting fixes as a major problem (though it might be). However, most upstream security fixes have not even been marked as needed in stable branches, and in several cases the flaws have

Likewise. :-/ [...] Even when the guests are running known trusted code, that code might have its own security flaws. KVM then potentially provides a useful security boundary between a compromised

Hi Progress has been made on the upgrade of B@D to use LAVA 2017-7 (#114) - once this is complete, issues #84 and #115 will also be resolved. I have a

For the series: Reviewed-by: Chris Paterson <chris.paterson2@...>

Good point. Sorry for jumping the gun! Chris

Hi, I think the TSC should somehow provide the ok for the activity in order to escalate it to the board since it involves some expenses (material), as described in my proposal. Once I get the ok, I

Hello Agustin, Thank you for creating this. Do you want me (or other CIP members) to sign up for this workshop? Or is it assumed we'll be there anyway? Kind regards, Chris

Hi, one of the ToDos coming from the last CIP TSC meeting was to create the wiki page to manage the ELCE workshop. Waiting for the formal approval of the B@D 1:1 activity, I created the page taking

Hi, last week at Codethink we invested some effort in discussing the coming tasks in order to reach a high level plan at least until ELCE 2017. Due to level of uncertainty of some of the tasks ahead