From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Codethink: report weeks 6 and 7
Date: Mon, 19 Feb 2018 09:53:28 +0100 [thread overview]
Message-ID: <6359446.CMKDBkSaUH@linux-if6s> (raw)
Hi,
this is a summary of the CIP related work we've done the last couple of weeks:
## Kernel maintenance
* Reviewed patches from Renesas to add support for SMP and I?C masters
on R8A7743 SoC, and applied them to the CIP kernel branch
* Reviewed Robert's merge request for B at D
* Discussed opportunities for CIP member participation at DebConf
* Reviewed the changes in stable release 4.4.113 (but didn't yet merge
them)
## CIP testing
* Went through the open tickets and sent to backlog all those that are related
with B at D development.
** Confirmed #157 is still an issue: https://gitlab.com/cip-project/cip-testing/testing/issues/157
** Unable to replicate #170 so far: https://gitlab.com/cip-project/cip-testing/testing/issues/170
* Working on #173 opened by Zoran: https://gitlab.com/cip-project/cip-testing/
testing/issues/173
* B at D working with new kernelci version. Consolidation required.
** Latest kernel tested and report by e-mail sent to mailing list.
* Relaxed permissions in /etc/linaro to adapt them to B at D use case #165:
https://gitlab.com/cip-project/cip-testing/testing/issues/165
* Busybox updated to a newer version.
## Others
* Updated milestones in the CIP testing project to adapt them to the new
maintenance mode.
* Although our participation was approved, in the last minute a collision in
my schedule prevent me from attending to OpenExpo in Madrid. No one else can
so I communicated to the organization we cannot attend.
* Open question: should we send Gitlab notifications to the mailing list?
As usual you can fin more accurate info about our work by reading the journal:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/
journal
Best Regards
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
reply other threads:[~2018-02-19 8:53 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=6359446.CMKDBkSaUH@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