From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP testing and kernel maintenance report week 38 and 39
Date: Mon, 2 Oct 2017 15:29:43 +0200 [thread overview]
Message-ID: <59D23F47.8080707@codethink.co.uk> (raw)
In-Reply-To: <59D223C3.4030104@codethink.co.uk>
Hi,
On 02/10/17 13:32, Agustin Benito Bethencourt wrote:
> Hi,
>
> this is a a summary of the main tasks performed by the Codethink guys
> during the last couple of weeks. Due to vacations and sickness, we have
> been less active than usual.
>
> + Week 38 and 39 2017
>
> ++ Kernel Maintenance
>
> No significant progress.
I've got these points from Ben H.
* Reviewed and applied patches for new hardware support in 4.4
* Reviewed patches in 4.4-stable branch. The idea is to release a new
kernel soon (before ELCE hopefully).
Apologies for not including them in the original report. I haven't been
fully available last week.
>
> ++ CIP testing project
>
> * A script to populate initramfs created and merged. Now initramfs is
> built locally again with the new LAVA. Ben H. helped to solve this issue.
> ** #111 https://gitlab.com/cip-project/cip-testing/testing/issues/111
> ** #136 https://gitlab.com/cip-project/cip-testing/testing/issues/136
>
> * LAVA updated. The new release will come with 2017.7 version.
> ** tmp data now is cleared with the new LAVA version
> *** #84 https://gitlab.com/cip-project/cip-testing/testing/issues/84
> ** Verbosity comes with the new LAVA version
> *** #115 https://gitlab.com/cip-project/cip-testing/testing/issues/115
>
> +++ Other minor accomplishments
>
> * Added to known issues the health check 30 seconds waste
> ** #56 https://gitlab.com/cip-project/cip-testing/testing/issues/56
>
> * Support request solved. #129
> ** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/129
>
> * Identified a link on the LAVA page that needs to be changed
> ** #133 https://gitlab.com/cip-project/cip-testing/testing/issues/133
>
> ++ Other tasks
>
> * CIP workshop at ELCE
> ** Call for participation for the B at D 101 training session published.
> ** Material and set up required for the training session confirmed and
> discussed with the Linux Foundation.
>
> * Y2038 meeting at ELCE confirmed.
> ** Call for topics among CIP members sent.
> ** Some CIP Members has confirmed their presence. More to come.
>
> Best Regards
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-10-02 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 11:32 [cip-dev] CIP testing and kernel maintenance report week 38 and 39 Agustin Benito Bethencourt
2017-10-02 13:29 ` Agustin Benito Bethencourt [this message]
2017-10-05 8:51 ` 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=59D23F47.8080707@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 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.