Message ID | 20240625065032.595783-1-Adithya.Balakumar@toshiba-tsip.com |
---|---|
Headers | show |
Series | Set hash-seed for empty ext partition | expand |
25/06/2024 10:37, Jan Kiszka wrote: > Shouldn't we sync to a wic revision >= the one containing this? > > Jan > Hello Jan, This is our preferred process by default, but this commit is in oe-core master branch only for now. We should probably wait for release or backporting. We are currently using the latest Scarthgap LTS version 5.0 branch.
On 25.06.24 15:09, Anton Mikanovich wrote: > 25/06/2024 10:37, Jan Kiszka wrote: >> Shouldn't we sync to a wic revision >= the one containing this? >> >> Jan >> > Hello Jan, > > This is our preferred process by default, but this commit is in oe-core > master > branch only for now. We should probably wait for release or backporting. > > We are currently using the latest Scarthgap LTS version 5.0 branch. > Maybe propose the commit for 5.0-LTS branch and then sync that in? But if you are fine with taking this backport, I will not hold you back. It will be valuable for us, that is for sure. Jan
Hi Anton and Jan, Thanks for the feedback. Let me propose this patch to Scarthgap also. And once accepted in Scarthgap, I will share the patch with isar again. Thanks, Adithya -----Original Message----- From: Jan Kiszka <jan.kiszka@siemens.com> Sent: Tuesday, June 25, 2024 8:00 PM To: Anton Mikanovich <amikan@ilbers.de>; balakumar adithya(TSIP TEUR) <Adithya.Balakumar@toshiba-tsip.com>; isar-users@googlegroups.com Cc: hayashi kazuhiro(林 和宏 DME ○DIG□MPS○MP4) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; kunijadar shivanand(TSIP TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; ashrith sai(TSIP) <Sai.Sathujoda@toshiba-tsip.com> Subject: Re: [PATCH v1 0/1] Set hash-seed for empty ext partition On 25.06.24 15:09, Anton Mikanovich wrote: > 25/06/2024 10:37, Jan Kiszka wrote: >> Shouldn't we sync to a wic revision >= the one containing this? >> >> Jan >> > Hello Jan, > > This is our preferred process by default, but this commit is in > oe-core master branch only for now. We should probably wait for > release or backporting. > > We are currently using the latest Scarthgap LTS version 5.0 branch. > Maybe propose the commit for 5.0-LTS branch and then sync that in? But if you are fine with taking this backport, I will not hold you back. It will be valuable for us, that is for sure. Jan -- Siemens AG, Technology Linux Expert Center