From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Codethink report weeks 14 - 17
Date: Fri, 27 Apr 2018 16:29:56 +0100 [thread overview]
Message-ID: <87vacc1xcb.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <1566127.uQPWh3l9jc@linux-if6s> ("Agustín Benito Bethencourt"'s message of "Fri, 27 Apr 2018 10:53:45 +0200")
Hi,
Documentation updated - see below
Agust?n Benito Bethencourt <agustin.benito@codethink.co.uk> writes:
> Hi,
>
> several interesting accomplishments these past weeks. Here is the report about
> Codethink's activities at CIP.
>
> ## CIP kernel maintenance
>
> * New CIP kernel released: 4.4.126-cip22
>
> * Kernel configurations are now collected in Gitlab: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config
> ** Moxa's kernel configuration evaluation pending.
>
> * New cip-kernel sub-directory created in gitlab for kernel related repos:
> https://gitlab.com/cip-project/cip-kernel
>
> * Moxa developers on-boarding process to the CIP kernel maintenance team has
> started.
> ** Moxa developers can review patches having Ben H. as mentor through the cip-
> dev mailing list.
>
> ## CIP kernel testing
>
> * B at D now fully supports Renesas board #167
> ** There are no dependencies related with bitbake/YOCTO
> ** Set up description sent to Renesas asking for confirmation.
> ** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/167
> ** User's documentation pending.
This has now mostly been completed - the text has been updated
#181 has been opened - and is now closed
https://gitlab.com/cip-project/cip-testing/testing/issues/181
Robert
>
> * Tests reports sent to cip-testing-results now include the new board support.
>
> * Vagrant updated in B at D
>
> ## Other topics
>
> * Now the developers involved in kernel work are meeting weekly through IRC in
> the chat.freenode.net/#cip channel on Thursdays for 30 min.
> ** Yesterday's meeting log: https://irclogs.baserock.org/cip/%23cip.
> 2018-04-26.log.html#t2018-04-26T09:02:24
>
> * Ben H. has participated in several discussions and questions through
> different CIP channels related with Debian LTS, since he is part of that
> effort at the Debian project.
>
> * Ben H. and Agustin participated in the discussion that J. Colbert's article
> at LWN.net has generated: https://lwn.net/Articles/749530/
>
> * Talk related with the CIP kernel process approved by the OSSJ 2018 content
> committee:
> https://ossalsjp19.sched.com/event/EaYy/in-need-for-a-linux-kernel-maintained-for-a-very-long-time-cip-kernel-maintenance-overview-agustin-benito-bethencourt-codethink-ltd?iframe=no&w=100%&sidebar=yes&bg=no
>
> * Introductory talk about CIP at the OpenSouthCode (Open Source event in
> Malaga, Spain) approved: https://www.opensouthcode.org/conferences/
> opensouthcode2018/program/proposals/119
>
> Best Regards
next prev parent reply other threads:[~2018-04-27 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:53 [cip-dev] Codethink report weeks 14 - 17 Agustín Benito Bethencourt
2018-04-27 15:29 ` Robert Marshall [this message]
2018-04-30 7:35 ` Chris Paterson
2018-05-02 7:55 ` Robert Marshall
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=87vacc1xcb.fsf@ctlt579.codethink.co.uk \
--to=robert.marshall@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.