[linux-yocto][yocto-kernel-cache master][PATCH] global: Clean up is not set with =n
Upstream is dropping support for is not set, so we adjust our configs accordingly. Commit: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=for-next=55de8686df7ed2b5237867b130e30c728bbd9db4 Signed-off-by: He Zhe --- bsp/qemuarma15/qemuarma15.cfg | 2 +- features/security/security-x86_64.cfg | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bsp/qemuarma15/qemuarma15.cfg b/bsp/qemuarma15/qemuarma15.cfg index df8181ff..6fc92c6b 100644 --- a/bsp/qemuarma15/qemuarma15.cfg +++ b/bsp/qemuarma15/qemuarma15.cfg @@ -36,4 +36,4 @@ CONFIG_HIGHMEM=y CONFIG_ARM_AMBA=y CONFIG_ARM_THUMB=y -# CONFIG_FUNCTION_GRAPH_TRACER is not set +CONFIG_FUNCTION_GRAPH_TRACER=n diff --git a/features/security/security-x86_64.cfg b/features/security/security-x86_64.cfg index dad137f6..0f5c3621 100644 --- a/features/security/security-x86_64.cfg +++ b/features/security/security-x86_64.cfg @@ -1,4 +1,4 @@ # SPDX-License-Identifier: MIT # Modern libc no longer needs a fixed-position mapping in userspace, remove it as a possible target. -# CONFIG_LEGACY_VSYSCALL_EMULATE is not set +CONFIG_LEGACY_VSYSCALL_EMULATE=n CONFIG_LEGACY_VSYSCALL_NONE=y -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11277): https://lists.yoctoproject.org/g/linux-yocto/message/11277 Mute This Topic: https://lists.yoctoproject.org/mt/90927150/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] QA notification for completed autobuilder build (yocto-3.4.4.rc1)
Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.4.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. NUC 6 4. Edgerouter 5. Beaglebone ETA for completion next Tuesday, May 10. Thanks, Jay > -Original Message- > From: yocto@lists.yoctoproject.org On Behalf > Of Pokybuild User > Sent: Wednesday, 4 May, 2022 10:32 AM > To: yocto@lists.yoctoproject.org > Cc: qa-build-notificat...@lists.yoctoproject.org > Subject: [yocto] QA notification for completed autobuilder build (yocto- > 3.4.4.rc1) > > > A build flagged for QA (yocto-3.4.4.rc1) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.4.4.rc1 > > > Build hash information: > > bitbake: c2d8f9b2137bd4a98eb0f51519493131773e7517 > meta-agl: 8543843eeb47fa9b45786d3e09bf497fcd5f95e0 > meta-arm: 2623e69db362b357db45c343e6d504909552c2d5 > meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069 > meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400 > meta-intel: daf5c125a744d45d8fa395b576147edd5a714f5c > meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8 > meta-openembedded: 9a0caf5b09e14a28a54c3f8524d97530aeb8152c > meta-virtualization: bd7511c53b921c9ce4ba2fdb42778ca194ebc3e8 > oecore: 1a6f5e27249afb6fb4d47c523b62b5dd2482a69d > poky: 780eeec8851950ee6ac07a2a398ba937206bd2e4 > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57008): https://lists.yoctoproject.org/g/yocto/message/57008 Mute This Topic: https://lists.yoctoproject.org/mt/90880124/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder-helper v13] Add a banner on the old documentation docs. Script to add banners to the old docs and outdated dunfell docs
On Wed, 2022-05-04 at 12:08 +0100, Abongwa Amahnui Bonalais wrote:
>
> +
> +def add_banner_old_docs(dir):
> +exclude = []
> +for root, dirs, filenames in os.walk(dir):
> + # exclude banner for 3.1.x upward as it is an LTS release and is
> still supported
> +exclude = [ name for name in os.listdir(dir) if
> name.startswith('3.1') ]
> +for d in dirs:
> +if d in exclude:
> +dirs.remove(d)
> +for filename in filenames:
> +if filename.endswith('.html'):
> +with open(os.path.join(root, filename), 'r',
> encoding="ISO-8859-1") as f:
> +current_content = f.read()
> +with open(os.path.join(root, filename), 'w') as f:
This is definitely getting there, thanks!
One small thing, shouldn't we write the files with the same encoding as we read
them?
> +f.write(current_content.replace('', '' +
> html_content))
> +f.write(current_content.replace('', last_div +
> ''))
> +if filename.endswith('.css'):
> +with open(os.path.join(root, filename), 'r',
> encoding="ISO-8859-1") as f:
> +css_content = f.read()
> +with open(os.path.join(root, filename), 'w') as f:
> +
> f.write(css_content.replace(css_content[css_content.find('body
> {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
> +add_banner_old_docs('.')
> +
> +
> +
> +
> +def dunfell_docs(dir):
> +dunfell_banners = []
> +for root, dirs, filenames in os.walk(dir):
> +dunfell_banners = [ name for name in os.listdir(dir) if not
> name.startswith('3.1') ]
> +for d in dirs:
> +if d in dunfell_banners:
> +dirs.remove(d)
> +for filename in filenames:
> +if filename.endswith('.html'):
> +with open(os.path.join(root, filename), 'r',
> encoding="ISO-8859-1") as f:
> +current_content = f.read()
> +with open(os.path.join(root, filename), 'w') as f:
> +f.write(current_content.replace('', '' +
> html_content_dunfell))
> +f.write(current_content.replace('', last_div +
> ''))
> +if filename.endswith('.css'):
> +with open(os.path.join(root, filename), 'r',
> encoding="ISO-8859-1") as f:
> +css_content = f.read()
> +with open(os.path.join(root, filename), 'w') as f:
> +
> f.write(css_content.replace(css_content[css_content.find('body
> {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
I think Quentin also mentioned that these two loop functions can be merged
together to form simpler code with a condition in the centre section?
> +dunfell_docs('.')
> \ No newline at end of file
We can add a newline at the end to avoid that.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57007): https://lists.yoctoproject.org/g/yocto/message/57007
Mute This Topic: https://lists.yoctoproject.org/mt/90884595/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Minutes: Yocto Project Weekly Triage Meeting 5/5/2022
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage *Attendees: *Randy, Richard, Luca Ceresoli, Bruce Ashfield, Michael Opdenacker, Ross Burton, Steve Sakoman, Tim Orling, Joshua Watt, Pavel, Aryaman Gupta *ARs:* Randy: talk to David Reyna to reassign his toaster bugs Richard: review the bugs from the old milestone ** *Notes:* N/A* * ** *Medium+ 4.1 Unassigned Enhancements/Bugs: *75 (Last week 77) *Medium+ 4.99 Unassigned Enhancements/Bugs: *48**(Last week 48) *AB Bugs: *48 (Last week 48) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57006): https://lists.yoctoproject.org/g/yocto/message/57006 Mute This Topic: https://lists.yoctoproject.org/mt/90913652/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
Demo apps is the least of the worst. They also add benchmarks, make tweaks to components that are in distribution (rather than hardware support) scope, and even go ahead and define their own distributions, and then make it impossible or very difficult to separate the distro from the BSP. Oh, and all of this on top of yocto from 2014. That's where the 'vendor from hell' moniker comes from. Alex On Thu, 5 May 2022 at 12:22, csimmonds wrote: > > BSP is not a well defined term in embedded Linux. Back in the day, Montavista > tried to popularise the term LSP, meaning Linux Support Package but it never > caught on. These days, BSP generally means all the things you need to run a > basic system. So that's bootloader, device tree, kernel config, kernel > patches (if any), and firmware blobs. It can also include user space config > such as video codecs, opengl libraries, and systemd units to start the > respective daemons. > > SoC and SoM vendors often overload their OE BSPs with irrelevant demo apps as > well. Constant bugbear of system integrators. > > HTH, > Chris > > On 5 May 2022 10:51:39 BST, "jchludzinski via lists.yoctoproject.org" > wrote: >> >> OK, let me try this: >> >> With other embedded OS's, the hardware specifics that are in the BSP are in >> the device trees in Linux. I assume the BSP's for OE Linux are rather simple? >> >> >> >> On 2022-05-05 04:47, Josef Holzmayr wrote: >>> >>> Howdy! >>> >>> Am Do., 5. Mai 2022 um 10:43 Uhr schrieb jchludzinski via >>> lists.yoctoproject.org >>> : OK, let's go with that. I've watched the "Live Coding with Yocto Project #1: download and first build" youtube video. Where is the BSP built in this procedure? >>> >>> >>> The BSP that is implicitly used in that video is the generic QEMU one, >>> which comes included with poky. Technically speaking, it lives in >>> https://git.yoctoproject.org/poky/tree/meta/conf/machine and >>> https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.15.bb >>> >>> A BSP can be many things, and this one is a rather small one, as >>> booting into and running linux on QEMU doesn't need patching and all >>> that, so in that case it comes pretty close to the perfect world that >>> Michael mentioned. >>> >>> Greetz, >>> Josef (who did that video, actually) >>> On 2022-05-05 03:16, Michael Opdenacker via lists.yoctoproject.org wrote: > > On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: >> >> A board-support-package (BSP) is software that provides a layer of >> abstraction from the physical board specifics for the host embedded OS >> (e.g., VXworks). >> >> I believe the device tree files (*.dts, *dtsi) in OE Linux provide the >> same function. It allows to OE kernel code to be independent of device >> specifics. > > > > The Device Tree files are just descriptions of the hardware. In a > perfect world, you could indeed use the same mainline kernel to support > all possible devices. However, that kernel would be unnecessarily big > for your custom system. You most probably want to customize its > configuration, and may also need custom kernel drivers and patches. > There's also the need for a bootloader compiled for your platform. > > That's why we need BSPs :-) > > Cheers, > Michael. > > > >>> >>> >>> > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57005): https://lists.yoctoproject.org/g/yocto/message/57005 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
BSP is not a well defined term in embedded Linux. Back in the day, Montavista tried to popularise the term LSP, meaning Linux Support Package but it never caught on. These days, BSP generally means all the things you need to run a basic system. So that's bootloader, device tree, kernel config, kernel patches (if any), and firmware blobs. It can also include user space config such as video codecs, opengl libraries, and systemd units to start the respective daemons. SoC and SoM vendors often overload their OE BSPs with irrelevant demo apps as well. Constant bugbear of system integrators. HTH, Chris On 5 May 2022 10:51:39 BST, "jchludzinski via lists.yoctoproject.org" wrote: >OK, let me try this: > >With other embedded OS's, the hardware specifics that are in the BSP are in >the device trees in Linux. I assume the BSP's for OE Linux are rather simple? > > > >On 2022-05-05 04:47, Josef Holzmayr wrote: >> Howdy! >> >> Am Do., 5. Mai 2022 um 10:43 Uhr schrieb jchludzinski via >> lists.yoctoproject.org >> : >>> >>> OK, let's go with that. >>> >>> I've watched the "Live Coding with Yocto Project #1: download and first >>> build" youtube video. Where is the BSP built in this procedure? >> >> The BSP that is implicitly used in that video is the generic QEMU one, >> which comes included with poky. Technically speaking, it lives in >> https://git.yoctoproject.org/poky/tree/meta/conf/machine and >> https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.15.bb >> >> A BSP can be many things, and this one is a rather small one, as >> booting into and running linux on QEMU doesn't need patching and all >> that, so in that case it comes pretty close to the perfect world that >> Michael mentioned. >> >> Greetz, >> Josef (who did that video, actually) >> >>> >>> >>> >>> On 2022-05-05 03:16, Michael Opdenacker via lists.yoctoproject.org >>> wrote: >>> > On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: >>> >> A board-support-package (BSP) is software that provides a layer of >>> >> abstraction from the physical board specifics for the host embedded OS >>> >> (e.g., VXworks). >>> >> >>> >> I believe the device tree files (*.dts, *dtsi) in OE Linux provide the >>> >> same function. It allows to OE kernel code to be independent of device >>> >> specifics. >>> > >>> > >>> > The Device Tree files are just descriptions of the hardware. In a >>> > perfect world, you could indeed use the same mainline kernel to support >>> > all possible devices. However, that kernel would be unnecessarily big >>> > for your custom system. You most probably want to customize its >>> > configuration, and may also need custom kernel drivers and patches. >>> > There's also the need for a bootloader compiled for your platform. >>> > >>> > That's why we need BSPs :-) >>> > >>> > Cheers, >>> > Michael. >>> > >>> > >>> > >>> >>> >>> >> >> >> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57004): https://lists.yoctoproject.org/g/yocto/message/57004 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
OK, let me try this: With other embedded OS's, the hardware specifics that are in the BSP are in the device trees in Linux. I assume the BSP's for OE Linux are rather simple? On 2022-05-05 04:47, Josef Holzmayr wrote: Howdy! Am Do., 5. Mai 2022 um 10:43 Uhr schrieb jchludzinski via lists.yoctoproject.org : OK, let's go with that. I've watched the "Live Coding with Yocto Project #1: download and first build" youtube video. Where is the BSP built in this procedure? The BSP that is implicitly used in that video is the generic QEMU one, which comes included with poky. Technically speaking, it lives in https://git.yoctoproject.org/poky/tree/meta/conf/machine and https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.15.bb A BSP can be many things, and this one is a rather small one, as booting into and running linux on QEMU doesn't need patching and all that, so in that case it comes pretty close to the perfect world that Michael mentioned. Greetz, Josef (who did that video, actually) On 2022-05-05 03:16, Michael Opdenacker via lists.yoctoproject.org wrote: > On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: >> A board-support-package (BSP) is software that provides a layer of >> abstraction from the physical board specifics for the host embedded OS >> (e.g., VXworks). >> >> I believe the device tree files (*.dts, *dtsi) in OE Linux provide the >> same function. It allows to OE kernel code to be independent of device >> specifics. > > > The Device Tree files are just descriptions of the hardware. In a > perfect world, you could indeed use the same mainline kernel to support > all possible devices. However, that kernel would be unnecessarily big > for your custom system. You most probably want to customize its > configuration, and may also need custom kernel drivers and patches. > There's also the need for a bootloader compiled for your platform. > > That's why we need BSPs :-) > > Cheers, > Michael. > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57003): https://lists.yoctoproject.org/g/yocto/message/57003 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
Howdy! Am Do., 5. Mai 2022 um 10:43 Uhr schrieb jchludzinski via lists.yoctoproject.org : > > OK, let's go with that. > > I've watched the "Live Coding with Yocto Project #1: download and first > build" youtube video. Where is the BSP built in this procedure? The BSP that is implicitly used in that video is the generic QEMU one, which comes included with poky. Technically speaking, it lives in https://git.yoctoproject.org/poky/tree/meta/conf/machine and https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.15.bb A BSP can be many things, and this one is a rather small one, as booting into and running linux on QEMU doesn't need patching and all that, so in that case it comes pretty close to the perfect world that Michael mentioned. Greetz, Josef (who did that video, actually) > > > > On 2022-05-05 03:16, Michael Opdenacker via lists.yoctoproject.org > wrote: > > On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: > >> A board-support-package (BSP) is software that provides a layer of > >> abstraction from the physical board specifics for the host embedded OS > >> (e.g., VXworks). > >> > >> I believe the device tree files (*.dts, *dtsi) in OE Linux provide the > >> same function. It allows to OE kernel code to be independent of device > >> specifics. > > > > > > The Device Tree files are just descriptions of the hardware. In a > > perfect world, you could indeed use the same mainline kernel to support > > all possible devices. However, that kernel would be unnecessarily big > > for your custom system. You most probably want to customize its > > configuration, and may also need custom kernel drivers and patches. > > There's also the need for a bootloader compiled for your platform. > > > > That's why we need BSPs :-) > > > > Cheers, > > Michael. > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57002): https://lists.yoctoproject.org/g/yocto/message/57002 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
OK, let's go with that. I've watched the "Live Coding with Yocto Project #1: download and first build" youtube video. Where is the BSP built in this procedure? On 2022-05-05 03:16, Michael Opdenacker via lists.yoctoproject.org wrote: On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: A board-support-package (BSP) is software that provides a layer of abstraction from the physical board specifics for the host embedded OS (e.g., VXworks). I believe the device tree files (*.dts, *dtsi) in OE Linux provide the same function. It allows to OE kernel code to be independent of device specifics. The Device Tree files are just descriptions of the hardware. In a perfect world, you could indeed use the same mainline kernel to support all possible devices. However, that kernel would be unnecessarily big for your custom system. You most probably want to customize its configuration, and may also need custom kernel drivers and patches. There's also the need for a bootloader compiled for your platform. That's why we need BSPs :-) Cheers, Michael. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57001): https://lists.yoctoproject.org/g/yocto/message/57001 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
On 5/5/22 08:39, jchludzinski via lists.yoctoproject.org wrote: > A board-support-package (BSP) is software that provides a layer of > abstraction from the physical board specifics for the host embedded OS > (e.g., VXworks). > > I believe the device tree files (*.dts, *dtsi) in OE Linux provide the > same function. It allows to OE kernel code to be independent of device > specifics. The Device Tree files are just descriptions of the hardware. In a perfect world, you could indeed use the same mainline kernel to support all possible devices. However, that kernel would be unnecessarily big for your custom system. You most probably want to customize its configuration, and may also need custom kernel drivers and patches. There's also the need for a bootloader compiled for your platform. That's why we need BSPs :-) Cheers, Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57000): https://lists.yoctoproject.org/g/yocto/message/57000 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OE Linux & board-support-package
A board-support-package (BSP) is software that provides a layer of abstraction from the physical board specifics for the host embedded OS (e.g., VXworks). I believe the device tree files (*.dts, *dtsi) in OE Linux provide the same function. It allows to OE kernel code to be independent of device specifics. On 2022-05-05 01:54, Zoran Stojsavljevic wrote: Hello J, Please, could you be more specific? Thank you, Zee ___ On Thu, May 5, 2022 at 5:42 AM jchludzinski via lists.yoctoproject.org wrote: OE Linux uses device tree files (*.dts and *.dtsi files), so is there any need for a board-support-package? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56999): https://lists.yoctoproject.org/g/yocto/message/56999 Mute This Topic: https://lists.yoctoproject.org/mt/90904726/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.4.rc1)
On Thu, 2022-05-05 at 01:15 +, Teoh, Jay Shen wrote: > Hi TSC, > > Intel and WR are good for QA execution. > Shall we proceed? Yes please, the TSC is concerned but doesn't believe there is much we can do about these issues and that they shouldn't affect the release quality. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56998): https://lists.yoctoproject.org/g/yocto/message/56998 Mute This Topic: https://lists.yoctoproject.org/mt/90882993/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
