From: der.herr@hofr.at (Nicholas Mc Guire)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel configurations in the CIP project
Date: Fri, 5 Oct 2018 04:10:38 +0000 [thread overview]
Message-ID: <20181005041038.GB30868@osadl.at> (raw)
In-Reply-To: <1538661106.3024.266.camel@codethink.co.uk>
On Thu, Oct 04, 2018 at 02:51:46PM +0100, Ben Hutchings wrote:
> On Wed, 2018-10-03 at 08:33 +0900, Daniel Sangorrin wrote:
> > Hello Lukas,
> >
> > > -----Original Message-----
> > > From: cip-dev-bounces at lists.cip-project.org
> > > Hi Robert,
> > >
> > > If I recall our conversation and follow the discussion on cip-dev correctly, you are still
> > > maintaining the test builds and infrastructure from the CIP project, right?
> > >
> > > Could you provide to Markus Kreidl, Nicholas McGuire (see CC) and me the kernel
> > > configurations you use in the test builds for the different CIP members?
> >
> > Not sure about the configs that Robert uses for testing, but the configurations from CIP members can be found here.
> > https://gitlab.com/cip-project/cip-kernel/cip-kernel-config
> [...]
>
> I think these are the configurations that Lukas needs - they are the
> configurations that should be used for determining whether commits are
> relevant to CIP.
>
ok - we started playing with them the siemens iot config seems very large to me is that
a designed config or did that "happen" ?
thx!
hofrat
next prev parent reply other threads:[~2018-10-05 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 18:53 [cip-dev] Kernel configurations in the CIP project Lukas Bulwahn
2018-10-02 23:33 ` Daniel Sangorrin
2018-10-04 13:51 ` Ben Hutchings
2018-10-04 21:48 ` Lukas Bulwahn
2018-10-05 4:10 ` Nicholas Mc Guire [this message]
2018-10-08 12:33 ` Jan Kiszka
2018-10-09 15:26 ` Nicholas Mc Guire
2018-10-04 11:43 ` 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=20181005041038.GB30868@osadl.at \
--to=der.herr@hofr.at \
--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