public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Progress on the CIP kernel maintenance and testing for your ELC talk
Date: Tue, 13 Mar 2018 15:58:45 +0100	[thread overview]
Message-ID: <52450414.TvpEuUOuAV@linux-if6s> (raw)

Hi Yoshi,

since you usually provide an update of the technical work done within CIP in 
your talks, here are some bullet points you can add in tomorrow's talk at ELC 
if you like.

## Kernel maintenance

* CIP 4.4.120-cip20 released last week.

Link: https://gitlab.com/cip-project/linux-cip

Comment: Ben Hutchings, from Codethink, releases a kernel version every 4 to 6 
weeks approx., depending on the amount and relevance of upstream patches 
landing on 4.4 LTS. Ben H. collaborates in the 4.4 LTS process directly.

* Effort in ensuring Meltdown and Spectre fixes land in the CIP kernel and CIP 
Members are informed about the current situation.

* Review of platform specific backported patches, specially from Renesas 
platforms.

Comment: Renesas backports patches to 4.4 from mainline that are reviewed and 
merged into CIP kernel when appropriate.

* CIP 4.4.120-cip120-rt13 released

Link: git://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git

Comment: I would name Daniel Wagner, Siemens, as maintainer and say a few 
words about the release process if you have time.

## Kernel testing

* B at D is being updated to include the latest kernelci

Link: https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/
merge_requests/53

* Work in progress to support Renesas iw20gm in B at D in the coming weeks. 

Link: https://gitlab.com/cip-project/cip-testing/testing/issues/167

* Improvements in networking and Vagrant configurations.

* Next steps: deployment through containers.

* B at D description and deploy.

Description: https://wiki.linuxfoundation.org/civilinfrastructureplatform/
ciptestingboardatdesksingledevfeaturepage

Deploy: https://wiki.linuxfoundation.org/civilinfrastructureplatform/
ciptestingboardatdeskdingledevdeployment#b-d-deployment-method-2-building-vm-
from-scratch-using-vagrant-15

Any additional feedback from participants on this list is welcome.

Best Regards
-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd

             reply	other threads:[~2018-03-13 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 14:58 Agustín Benito Bethencourt [this message]
2018-03-13 16:26 ` [cip-dev] Progress on the CIP kernel maintenance and testing for your ELC talk Zoran S
2018-03-23 10:55   ` Chris Paterson
2018-03-23 14:19     ` Zoran S
2018-03-23 14:25       ` Robert Marshall
2018-03-23 14:39         ` Zoran S
2018-03-23 15:09           ` Tom Pollard
2018-03-27  7:39             ` Zoran S
2018-03-23 15:53           ` Robert Marshall
2018-03-27 12:26             ` Zoran S
2018-03-14  5:55 ` KOBAYASHI Yoshitake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52450414.TvpEuUOuAV@linux-if6s \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox