[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 8/9] features/intel-persistent-memory: remove CONFIG_ND_BLK

From: Yongxin Liu In kernel commit f8669f1d6a86 (nvdimm/blk: Delete the block-aperture window driver), block data window device support was removed for NVDIMM. Signed-off-by: Yongxin Liu --- features/intel-persistent-memory/intel-x86-64-pmem.cfg | 1 - 1 file changed, 1 deletion(-) diff

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 9/9] features/intel-persistent-memory: remove CONFIG_DEV_DAX_PMEM_COMPAT

From: Yongxin Liu In kernel commit 83762cb5c7c4 ("dax: Kill DEV_DAX_PMEM_COMPAT"), the /sys/class/dax compatibility option was deleted. Signed-off-by: Yongxin Liu --- features/intel-persistent-memory/intel-x86-64-dax.cfg | 1 - 1 file changed, 1 deletion(-) diff --git

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 7/9] bsp/intel-x86: replace old configs of Intel SPI controller

From: Yongxin Liu In kernel commit e23e5a05d1fd ("mtd: spi-nor: intel-spi: Convert to SPI MEM"), the configs for Intel SPI were changed. Old: CONFIG_SPI_INTEL_SPI_PCI CONFIG_SPI_INTEL_SPI_PLATFORM New: CONFIG_SPI_INTEL_PCI CONFIG_SPI_INTEL_PLATFORM Signed-off-by: Yongxin

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 6/9] bsp/intel-x86: remove cleancache

From: Yongxin Liu In kernel commit 0a4ee518185e ("mm: remove cleancache"), the cleancache subsystem was removed. Signed-off-by: Yongxin Liu --- bsp/intel-x86/intel-x86.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg index

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 5/9] kernel-cache: enable kernel configs to support for editing socket buffer's priority

From: Meng Li To edit a socket buffer's priority using tc, it needs to enable below 2 configs. CONFIG_NET_EMATCH=y CONFIG_NET_ACT_SKBEDIT=y Signed-off-by: Meng Li Signed-off-by: Bruce Ashfield (cherry picked from commit 4c1d7cd3a96b9a022624da376febf75ac08448ea) Signed-off-by: Yongxin Liu ---

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 2/9] bsp/intel-x86: add support for Marvell Alaska PHYs

Signed-off-by: Yongxin Liu --- bsp/intel-x86/intel-x86.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg index 2d4c005e..34206353 100644 --- a/bsp/intel-x86/intel-x86.cfg +++ b/bsp/intel-x86/intel-x86.cfg @@ -364,3 +364,6 @@

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 4/9] bsp/intel-x86: add support for Time-Sensitive Network

Signed-off-by: Yongxin Liu --- bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 + 1 file changed, 1 insertion(+) diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc b/bsp/intel-x86/intel-x86-64-preempt-rt.scc index 38331ac8..197b5064 100644 --- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc +++

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 1/9] bsp/intel-x86: change the i2c-hid configuration to be ACPI-based

The i2c-hid driver has been split in kernel commit b33752c30023 ("HID: i2c-hid: Reorganize so ACPI and OF are separate modules"). We use ACPI-based driver only in intel-x86 BSP. Fix the following warning: [INFO]: the following symbols were not found in the active configuration: -

[linux-yocto][yocto-kernel-cache][master and yocto-6.1][PATCH 3/9] features/intel-pinctrl: add pinctrl driver for Intel Elkhart Lake

Signed-off-by: Yongxin Liu --- features/intel-pinctrl/intel-pinctrl.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/features/intel-pinctrl/intel-pinctrl.cfg b/features/intel-pinctrl/intel-pinctrl.cfg index 491aca89..c6a3e7ab 100644 --- a/features/intel-pinctrl/intel-pinctrl.cfg +++

[yocto] Yocto Project Status 7 February 2023 (WW06)

Current Dev Position: YP 4.2 M3 Next Deadline: 20th February 2023 YP 4.2 M3 Build Next Team Meetings: * Bug Triage meeting Thursday February 9th 7:30 am PDT (

[yocto] [autobuilder][PATCH v2 3/3] scripts/send-qa-email: add target and base revisions in regression report

From: Alexis Lothoré Current regression reports do not contain information about versions compared when generating reports. While it is still possible to get the information by searching the autobuilder log, it is not convenient. Moreover, future developments will allow to generate multiple

[yocto] [autobuilder][PATCH v2 2/3] scripts/send-qa-email: reduce testresults shallow clone depth

From: Alexis Lothoré Since we are now force-fetching base revisions and target revisions for regression report generation, we can make testresults clone even more "shallow" to increase clone speed in CI pipelines Signed-off-by: Alexis Lothoré --- scripts/send_qa_email.py | 4 ++-- 1 file

[yocto] [autobuilder][PATCH v2 1/3] scripts/send-qa-email: force current revision fetch

From: Alexis Lothoré If we try to run send-qa-email to simulate past releases (for example, for development or debugging), the execution will very likely fail because the target revision to examine (ie: the poky revision) is too old, and as a consequence is not contained in the testresults

[yocto] [autobuilder][PATCH v2 0/3] ease send-qa-email usage with older history

From: Alexis Lothoré Hello, This is the v2 of minor patch series to ease development/debugging on send-qa-email. There is no functional change in the patches since v1, those are resent to fix some mess in signedoff/from fields from my email configuration. Regards, Alexis Lothoré (3):

Re: [yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

On Tue, 2023-02-07 at 15:52 +0100, Alexis Lothoré wrote: > Hello Richard, > > On 2/7/23 15:42, Richard Purdie wrote: > > On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via > > lists.yoctoproject.org wrote: > > > I assumed that no tool is currently trying to parse the regression > > > reports,

Re: [yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

Hello Richard, On 2/7/23 15:42, Richard Purdie wrote: > On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via > lists.yoctoproject.org wrote: >> I assumed that no tool is currently trying to parse the regression reports, >> so >> I chose arbitrarily the metadata format. > > The reports have

Re: [yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > Hello, > this minor patch series bring minor fixes into send-qa-email to ease > development/debugging in it: > - fetching current build test results works well in CI builds because we are > sure that the build

[yocto] [autobuilder][PATCH 3/3] scripts/send-qa-email: add target and base revisions in regression report

Current regression reports do not contain information about versions compared when generating reports. While it is still possible to get the information by searching the autobuilder log, it is not convenient. Moreover, future developments will allow to generate multiple reports (with different

[yocto] [autobuilder][PATCH 2/3] scripts/send-qa-email: reduce testresults shallow clone depth

Since we are now force-fetching base revisions and target revisions for regression report generation, we can make testresults clone even more "shallow" to increase clone speed in CI pipelines Signed-off-by: Alexis Lothoré Signed-off-by: Alexis Lothore --- scripts/send_qa_email.py | 4 ++-- 1

[yocto] [autobuilder][PATCH 1/3] scripts/send-qa-email: force current revision fetch

If we try to run send-qa-email to simulate past releases (for example, for development or debugging), the execution will very likely fail because the target revision to examine (ie: the poky revision) is too old, and as a consequence is not contained in the testresults shallow clone anymore

[yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

Hello, this minor patch series bring minor fixes into send-qa-email to ease development/debugging in it: - fetching current build test results works well in CI builds because we are sure that the build results will be in the 5 upper commits of testsresults repository shallow clone (because it