From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Update week 49
Date: Fri, 9 Dec 2016 16:01:34 +0100 [thread overview]
Message-ID: <584AC74E.8080109@codethink.co.uk> (raw)
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 Portland in February
** Testing effort status
++ Kernel Maintenance
* First backports to provide hardware support for Beaglebone Black sent
to the list for comments and evaluation.
* CIP repository already mirrored in Gitlab.com:
https://gitlab.com/cip-project/linux-cip/commits/linux-4.4.y-cip Thanks
Yoshi!
++ Testing
* Progress in the VM with kernelci
** Have browser on host able to view kernelci pages
** Some work (not yet complete) on getting this setup to happen on
provisioning of the vm).
** Investigating issues with retrieving the build artifacts.
** Installing of lava2 on the vm
* Added a project in Gitlab.com to mirror the kernelci front end repository.
* Introduction to CIP testing effort published on the wiki:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting
++ Other topics
* Robert Marshall, that is currently working on the kernelci VM will be
at FOSDEM, like myself.
++ Next Tasks
* In the coming days CIP kernel will update from 4.4.30 to 4.4.37 Once
we have testing in place it will make sense to test every release and
update as soon as is everything ok from our side.
* Keep working on the kernelci VM
* Patches review/merge
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
reply other threads:[~2016-12-09 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=584AC74E.8080109@codethink.co.uk \
--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