All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org,
	nobuhiro1.iwamatsu@toshiba.co.jp
Subject: Re: [cip-dev] [isar-cip-core] tests: put all tests into a opt layer
Date: Wed, 22 Jul 2020 10:04:51 +0200	[thread overview]
Message-ID: <b22e4826-c624-fe98-07ee-2d6d99bf55a1@siemens.com> (raw)
In-Reply-To: <OSBPR01MB20537A054E7222BF5E1BC7E6D0790@OSBPR01MB2053.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

On 22.07.20 09:25, daniel.sangorrin@toshiba.co.jp wrote:
> ________________________________________
> From: Jan Kiszka <jan.kiszka@siemens.com>
> Sent: Wednesday, July 22, 2020 3:44 PM
> To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □SWC◯ACT); iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
> Subject: Re: [cip-dev] [isar-cip-core] tests: put all tests into a opt layer
> 
> On 21.07.20 14:42, Daniel Sangorrin wrote:
>> having an opt-tests layer makes it easier to see what
>> tests are installed, and allows creating images without
>> them as well
> 
> JAN:
> "Having ... as well."
> 
> Does this obsolete
> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/merge_requests/7,
> where I just commented on?
> 
> DANIEL: Maybe you can apply Iwamatsu-san merge request first, and I will prepare a new patch on top of that to avoid confusion.

That would confuse me now: What creating a separate test image first,  
just to remove it again?

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 (#4957): https://lists.cip-project.org/g/cip-dev/message/4957
Mute This Topic: https://lists.cip-project.org/mt/75702560/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]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-07-22  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 12:42 [cip-dev] [isar-cip-core] tests: put all tests into a opt layer Daniel Sangorrin
2020-07-22  6:44 ` Jan Kiszka
2020-07-22  7:25   ` Daniel Sangorrin
2020-07-22  8:04     ` Jan Kiszka [this message]
2020-07-22 10:46       ` Daniel Sangorrin
2020-07-22 14:07         ` Jan Kiszka
2020-07-28 23:36           ` Daniel Sangorrin

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=b22e4826-c624-fe98-07ee-2d6d99bf55a1@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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.