From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Report weeks 45, 46 and 47
Date: Mon, 27 Nov 2017 21:12:04 +0100 [thread overview]
Message-ID: <5A1C7194.5090203@codethink.co.uk> (raw)
Dear CIP friends,
On week 46 I updated the CIP TSC about progress on the Kernel
Maintenance front but did not do it here.
++ Kernel Maintenance
* Ben H. sent notes on Y2038 meeting and various talks to the cip-dev list
* CIP kernel version 4.4.98-cip13 released
** Ben H. Reviewed changes in Linux 4.4.93-4.4.98 inclusive.
** Applied patches to remove firmware from kernel source.
** watchdog feature backport (v2) from Siemens reviewed and applied
** kernel security tracker updated.
** Backported various security fixes and sent them to Greg Kroah-Hartman
for the 4.4 stable branch
* Future CIP kernel maintainers training
** Patch review guidelines in progress, as first step towards training
kernel devs from Members as future CIP kernel maintainers in progress.
* Kernel maintenance wiki page reviewed. Agustin will update it.
++ CIP Testing project
* Robert Marshall has been doing some support on this list.
* Went over the open tasks and documenting them to be pick up when the
project gets re-started.
** Agustin sent a mail on this mailing list summarising:
*** CIP Testing project background.
*** Current status
*** Options for the future
As usual, you can follow our work more closely through the project journal.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
reply other threads:[~2017-11-27 20:12 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=5A1C7194.5090203@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.