From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Codethink: report weeks 11 to 13
Date: Tue, 03 Apr 2018 11:01:09 +0200 [thread overview]
Message-ID: <2713148.FT5Gb9a9MJ@linux-if6s> (raw)
Hi,
## CIP kernel maintenance
* Review of LTS patches on its way.
* Kernel configurations sent by Moxa to be reviewed.
## CIP kernel testing
* B at D Support for Renesas board
** Remote PDU working (#166). Timeout issues under investigation (#167)
*** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/166
*** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/167
## Other topics
* Meeting between Moxa and Codethink. The goal was to put Moxa up to speed and
find a place for them to start.
** Recommendation of kernel activities were sent prior to the event to SZLin.
** Based on the outcome executed by Moxa, it seems the meeting was useful.
* In order to share the journal at least with Moxa, the wiki page was moved:
#179
** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/179
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
next reply other threads:[~2018-04-03 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 9:01 Agustín Benito Bethencourt [this message]
2018-04-03 9:02 ` [cip-dev] Codethink: report weeks 11 to 13 Agustín Benito Bethencourt
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=2713148.FT5Gb9a9MJ@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