| Message ID | 20230620135657.4585-1-venkata.pyla@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | [isar-cip-core] kas-cip.yml: Update isar reference | expand |
On 20.06.23 15:56, venkata.pyla@toshiba-tsip.com wrote: > From: venkata pyla <venkata.pyla@toshiba-tsip.com> > > To bring the reproducible build issue fixes from the upstream > e.g.: vmlinux files are not reproducible in case of arm architectures > > Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com> > --- > kas-cip.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kas-cip.yml b/kas-cip.yml > index b6a3ded..454fe04 100644 > --- a/kas-cip.yml > +++ b/kas-cip.yml > @@ -22,7 +22,7 @@ repos: > > isar: > url: https://github.com/ilbers/isar.git > - refspec: f95f69d3b83cc28976ef81eeefb5ec5dd17e544f > + refspec: d2b961746be788f0f35f8297ed3a8d2292704a4c > layers: > meta: > Is this urgent to move on? Or should we wait for the Isar fix [1] to move to master or even beyond (there are some changes coming for OP-TEE & Co.)? Jan [1] https://groups.google.com/d/msgid/isar-users/892c6e34-bd87-04fa-1155-dad3fd060b93%40siemens.com
>-----Original Message----- >From: Jan Kiszka <jan.kiszka@siemens.com> >Sent: Tuesday, June 20, 2023 10:34 PM >To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba- >tsip.com>; cip-dev@lists.cip-project.org >Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba- >tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) ><kazuhiro3.hayashi@toshiba.co.jp> >Subject: Re: [isar-cip-core] kas-cip.yml: Update isar reference > >On 20.06.23 15:56, venkata.pyla@toshiba-tsip.com wrote: >> From: venkata pyla <venkata.pyla@toshiba-tsip.com> >> >> To bring the reproducible build issue fixes from the upstream >> e.g.: vmlinux files are not reproducible in case of arm architectures >> >> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com> >> --- >> kas-cip.yml | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/kas-cip.yml b/kas-cip.yml index b6a3ded..454fe04 100644 >> --- a/kas-cip.yml >> +++ b/kas-cip.yml >> @@ -22,7 +22,7 @@ repos: >> >> isar: >> url: https://github.com/ilbers/isar.git >> - refspec: f95f69d3b83cc28976ef81eeefb5ec5dd17e544f >> + refspec: d2b961746be788f0f35f8297ed3a8d2292704a4c >> layers: >> meta: >> > >Is this urgent to move on? Or should we wait for the Isar fix [1] to move to >master or even beyond (there are some changes coming for OP-TEE & Co.)? Not urgent, we can wait for it. You can ignore the patch from me, thanks for the information. > >Jan > >[1] >https://groups.google.com/d/msgid/isar-users/892c6e34-bd87-04fa-1155- >dad3fd060b93%40siemens.com > > >-- >Siemens AG, Technology >Competence Center Embedded Linux
On 21.06.23 06:38, Venkata.Pyla@toshiba-tsip.com wrote: > > >> -----Original Message----- >> From: Jan Kiszka <jan.kiszka@siemens.com> >> Sent: Tuesday, June 20, 2023 10:34 PM >> To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba- >> tsip.com>; cip-dev@lists.cip-project.org >> Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba- >> tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) >> <kazuhiro3.hayashi@toshiba.co.jp> >> Subject: Re: [isar-cip-core] kas-cip.yml: Update isar reference >> >> On 20.06.23 15:56, venkata.pyla@toshiba-tsip.com wrote: >>> From: venkata pyla <venkata.pyla@toshiba-tsip.com> >>> >>> To bring the reproducible build issue fixes from the upstream >>> e.g.: vmlinux files are not reproducible in case of arm architectures >>> >>> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com> >>> --- >>> kas-cip.yml | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/kas-cip.yml b/kas-cip.yml index b6a3ded..454fe04 100644 >>> --- a/kas-cip.yml >>> +++ b/kas-cip.yml >>> @@ -22,7 +22,7 @@ repos: >>> >>> isar: >>> url: https://github.com/ilbers/isar.git >>> - refspec: f95f69d3b83cc28976ef81eeefb5ec5dd17e544f >>> + refspec: d2b961746be788f0f35f8297ed3a8d2292704a4c >>> layers: >>> meta: >>> >> >> Is this urgent to move on? Or should we wait for the Isar fix [1] to move to >> master or even beyond (there are some changes coming for OP-TEE & Co.)? > Not urgent, we can wait for it. > > You can ignore the patch from me, thanks for the information. > FYI: [1] is merged now. OP-TEE patches are circling on the list, but I would expect them to be there a bit longer (1-2 weeks) for testing purposes. So, feel free to propose an update earlier. Jan
diff --git a/kas-cip.yml b/kas-cip.yml index b6a3ded..454fe04 100644 --- a/kas-cip.yml +++ b/kas-cip.yml @@ -22,7 +22,7 @@ repos: isar: url: https://github.com/ilbers/isar.git - refspec: f95f69d3b83cc28976ef81eeefb5ec5dd17e544f + refspec: d2b961746be788f0f35f8297ed3a8d2292704a4c layers: meta: