From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe
Date: Wed, 19 Aug 2020 00:00:50 +0000 [thread overview]
Message-ID: <OSBPR01MB2983A946DAAE7D3E25A87363925D0@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <e525e738-22ee-ce33-e515-23614bf82837@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
Hi,
> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
> Sent: Tuesday, August 18, 2020 10:56 PM
> To: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT) <nobuhiro1.iwamatsu@toshiba.co.jp>; cip-dev@lists.cip-project.org
> Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe
>
> On 18.08.20 15:47, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
> >> Sent: Tuesday, August 18, 2020 2:30 PM
> >> To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
> <nobuhiro1.iwamatsu@toshiba.co.jp>
> >> Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe
> >>
> >> On 18.08.20 06:57, Nobuhiro Iwamatsu wrote:
> >>> Hi Jan,
> >>>
> >>> Could you comment on this patch series?
> >>>
> >>
> >> Ah, yeah, sorry.
> >>
> >> I think now it's better to model that as extension of an image, given
> >> that we already have two (regular + security). Or will we implicitly
> >> test the security image via the regular one?
> >>
> >
> > I see.
> > When extended, the resulting image will have the same filename as the base.
> > It's difficult to distinguish, so it's implemented as it is now.
> > If you know how to change the generated image file name by yaml file, please let me know.
>
> Isar does not yet allow to override the image name. You'd basically have
> to weaken its setting like this
>
> [isar/meta/classes/image.bbclass]
> IMAGE_FULLNAME ?= "${PN}-${DISTRO}-${MACHINE}"
>
> and then you could override IMAGE_FULLNAME as desired.
I see. Thanks for your comment.
I will update function for allow to override IMAGE_FULLNAME, and I will resend the updated patch.
>
> Jan
>
Best regards,
Nobuhiro
> --
> 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 (#5134): https://lists.cip-project.org/g/cip-dev/message/5134
Mute This Topic: https://lists.cip-project.org/mt/75987091/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-08-19 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16281511DE955BB5.19258@lists.cip-project.org>
2020-08-18 4:57 ` [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe Nobuhiro Iwamatsu
2020-08-18 5:29 ` Jan Kiszka
2020-08-18 13:47 ` Nobuhiro Iwamatsu
2020-08-18 13:55 ` Jan Kiszka
2020-08-19 0:00 ` Nobuhiro Iwamatsu [this message]
2020-08-04 13:53 Nobuhiro Iwamatsu
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=OSBPR01MB2983A946DAAE7D3E25A87363925D0@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
/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.