public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Update week 44
Date: Mon, 7 Nov 2016 17:03:36 +0100	[thread overview]
Message-ID: <5820A5D8.9090803@codethink.co.uk> (raw)

Hi,

if you have any update not included in this mail, feel free to add it. I 
do not intend to provide a full weekly report but to inform about the 
activity I am aware of.

++ Meetings

* Members meeting on Monday Nov 31st

++ Kernel maintenance

* Week 44 is Plumbers week so Ben H., like many kernel hackers, are there.
* Link to CIP 4.4.27 kernel: 
https://git.kernel.org/cgit/linux/kernel/git/bwh/linux-cip.git

++ 4.4 LSK: evaluation of backported features

* In order to evaluate the features that has been already backported by 
Linaro to 4.4 kernel, that might be interested to CIP, please check the 
following links:
** List of backported features and other general information: 
https://wiki.linaro.org/LSK
** Backported features description: https://wiki.linaro.org/lsk/features
** Link to the LSK-4.4 repo: 
https://git.linaro.org/kernel/linux-linaro-stable.git/log/?h=linux-linaro-lsk-v4.4

++ Setting up kernelci to test CIP kernel

* No major progress this week.

++ Other topics

* A white paper is being written to develop the CIP charter. Once 
Members have something coherent that looks like a draft, I will publish 
it in the public wiki to receive your feedback.

Best Regards

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

             reply	other threads:[~2016-11-07 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 16:03 Agustin Benito Bethencourt [this message]
2016-11-10  9:12 ` [cip-dev] Update week 44 Agustin Benito Bethencourt
2016-11-10  9:24   ` Agustin 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=5820A5D8.9090803@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