From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel configurations for 4.19?
Date: Wed, 17 Apr 2019 12:53:05 +0100 [thread overview]
Message-ID: <1555501985.3557.26.camel@codethink.co.uk> (raw)
Please could members send their kernel configuration files for Linux
4.19-cip? Either send them to the list as attachments, or create merge
requests for
<https://gitlab.com/cip-project/cip-kernel/cip-kernel-config>.
There are already configuration files for 4.19 in cip-kernel-config
that were produced by automatically updating the 4.4 configurations.
Please also let us know which of these can be deleted.
Ben.
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next reply other threads:[~2019-04-17 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 11:53 Ben Hutchings [this message]
2019-04-19 6:03 ` [cip-dev] Kernel configurations for 4.19? daniel.sangorrin at toshiba.co.jp
2019-05-22 8:57 ` daniel.sangorrin at toshiba.co.jp
2019-05-09 10:11 ` Chris Paterson
2019-06-12 0:12 ` Masato Minda
2019-06-16 21:49 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-09 13:49 ` Ben Hutchings
2019-07-09 14:40 ` Ben Hutchings
2019-07-12 0:57 ` daniel.sangorrin at toshiba.co.jp
[not found] ` <7c8d175eaa43357d6484c6fee89c4d0f@codethink.co.uk>
[not found] ` <909b4353-87c9-08e2-46f1-4ef8ce3fb6d2@siemens.com>
2019-07-12 16:34 ` [cip-dev] Request for guidance: removal of old config files [was: Kernel configurations for 4.19?] Ben Hutchings
2019-07-14 22:42 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-21 16:25 ` Pavel Machek
2019-07-21 17:58 ` Zoran S
2019-07-21 18:28 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 9:28 [cip-dev] Kernel configurations for 4.19? Mauerer, Wolfgang
2019-07-09 14:01 ` Ben Hutchings
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=1555501985.3557.26.camel@codethink.co.uk \
--to=ben.hutchings@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