From: "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] isar-cip-core and cip-kernel-config
Date: Tue, 9 Jun 2020 11:25:22 +0000 [thread overview]
Message-ID: <TYAPR01MB2064955529EA8A3DF3B90702D0820@TYAPR01MB2064.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <e9ae3b47-7f38-0da3-b90c-b0b4dbdf1eae@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Good to know Jan, thanks for the update.
> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Jan Kiszka
> Sent: Tuesday, June 9, 2020 7:01 PM
> To: cip-dev <cip-dev@lists.cip-project.org>
> Subject: [cip-dev] isar-cip-core and cip-kernel-config
>
> Hi all,
>
> a quick follow-up from our cip-core meeting today:
>
> isar-cip-core is already able to pull configs from cip-kernel-config. It
> does so for all machines where USE_CIP_KERNEL_CONFIG = "1", ie.
> hihope-rzg2m, iwg20m and simatic-ipc227e. So we "only" need to check the
> other targets and see how they can be migrated.
>
> And we should remove the old defconfigs from isar-cip-core then (some
> could already go).
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4791): https://lists.cip-project.org/g/cip-dev/message/4791
Mute This Topic: https://lists.cip-project.org/mt/74770939/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-06-09 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:00 [cip-dev] isar-cip-core and cip-kernel-config Jan Kiszka
2020-06-09 11:25 ` Daniel Sangorrin [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-18 16:20 [cip-dev] : " Gylstorff Quirin
2020-02-20 11:06 ` Chris Paterson
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=TYAPR01MB2064955529EA8A3DF3B90702D0820@TYAPR01MB2064.jpnprd01.prod.outlook.com \
--to=daniel.sangorrin@toshiba.co.jp \
--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;
as well as URLs for NNTP newsgroup(s).