On 11/17/21 4:02 AM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Tue, Nov 16, 2021 at 11:03 AM Bruce Ashfield via
lists.yoctoproject.org
wrote:
On Tue, Nov 16, 2021 at 1:13 AM Xu, Yanfei wrote:
On 11/16/21 11:48 AM, Bruce Ashfield wrote:
Hi
On 11/16/21 11:48 AM, Bruce Ashfield wrote:
Hi Bruce,
We encountered a warning when compiling linux-yocto 5.10 in WRlinux on
our tester's server machine. After doing some search, I found yocto also
encountered this some years
ago.[https://patchwork.openembedded.org/patch/152442/] Maybe yocto
On 11/15/21 11:19 AM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Sun, Nov 14, 2021 at 9:21 PM Xu, Yanfei wrote:
Hi Bruce,
We encountered a warning when compiling linux-yocto 5.10 in WRlinux on
our tester's server machine. After doing some search
Hi Bruce,
We encountered a warning when compiling linux-yocto 5.10 in WRlinux on
our tester's server machine. After doing some search, I found yocto also
encountered this some years
ago.[https://patchwork.openembedded.org/patch/152442/] Maybe yocto also
have this warning now? I can't figure
On 10/21/21 9:41 AM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
In message: [linux-yocto][v5.10/standard/base][PATCH] iommu/arm-smmu-v3:
Ratelimit event dump
on 20/10/2021 Yanfei Xu wrote:
From: Jean-Philippe Brucker
When a device or driver
From: Jean-Philippe Brucker
When a device or driver misbehaves, it is possible to receive DMA fault
events much faster than we can print them out, causing a lock up of the
system and inability to cancel the source of the problem. Ratelimit
printing of events to help recovery.
Tested-by: Aaro
On 9/29/21 8:55 PM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Wed, Sep 29, 2021 at 5:31 AM Xu, Yanfei wrote:
On 9/28/21 9:28 PM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
I had done the same fix last
On 9/28/21 9:28 PM, Bruce Ashfield wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
I had done the same fix last Tuesday for 5.14, and hadn't gotten
around to cherry picking it yet:
Since the commit a653b0f0ab79 ("cpuset: Convert callback_lock to
raw_spinlock_t") has changed the lock type of callbak_lock to
raw_spinlock_t, we should use raw_spin_lock/unlock funciton for
accessing it.
Fixes: 10dfcfda5c6f ("cgroup/cpuset: Fix violation of cpuset locking rule")
Signed-off-by:
From: Pantelis Antoniou
commit ba900332d141bf2d1d3b6aa7da8f01fe4b9fb256 from
https://github.com/altera-opensource/linux-socfpga.git
Add a runtime interface to using configfs for generic device tree overlay
usage. With it its possible to use device tree overlays without having
to use a
On 8/10/21 6:30 PM, Bruce Ashfield wrote:
**[Please note: This e-mail is from an EXTERNAL e-mail address]
I already have the same automated conversion locally, but since I'm out
of the office, I haven't pushed it yet.
I see that I didn't push it to master-next, so I'll do that shortly.
This is the result of automated script conversion:
scripts/contrib/convert-overrides.py
converting the metadata to use ":" as the override character instead of
"_".
Signed-off-by: Yanfei Xu
---
recipes-tools/rt-app/rt-app.bb | 2 +-
recipes-tools/schedtool-dl/schedtool-dl.bb | 2
rw_semaphore is implemented with rt-mutex in rt-kernel which is
different from the standard kernel. Compatible with these two
implementations on aufs by adding a "#ifndef" statement.
The compile failure log as blow:
| CC drivers/char/hw_random/virtio-rng.o
| CC kernel/task_work.o
|
The commit b7a01a10d2f9 ("net: xfrm: Use sequence counter with
associated spinlock") change the type of xfrm_state_hash_generation
from "seqcount_t" to "seqcount_spinlock_t". Revert this commit
for fixing compile failure of "incompatible pointer type".
This reverts commit
From: Yanfei Xu
CONFIG_CC_OPTIMIZE_FOR_SIZE should be disabled when enable
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE. They are mutually exclusive.
This change can fix the following warning:
WARNING: linux-yocto-5.10.19+gitAUTOINC+67e74d52f2_5b86278250-r0
do_kernel_configcheck: [kernel config]:
From: Yanfei Xu
Commit:621e14659f37("can: flexcan: drop repetitive execution
can_rx_offload_add_timestamp") and commit:3713ba3e41db("s32: flexcan:
Remove duplicated code as part of kernel 5.4-rt initial merge") fix the
same flexcan bug in different way, and both of them are contained in
codes,
From: Yanfei Xu
After the commit 83521390e("s32: flexcan: Remove duplicated code as part
of kernel 5.4-rt initial merge"), the flexcan_mailbox_read() is not
invoked anymore. To avoid the below compile-time warning, let's remove it.
warning: 'flexcan_mailbox_read' defined but not
From: Yanfei Xu
Changing CONFIG_SCSI from '=m' to '=y' to be consistent with its
direct dependency, which is 'CONFIG_SCSI_VIRTIO=y' in virtio.cfg.
Signed-off-by: Yanfei Xu
---
bsp/qemu-ppc32/qemu-ppc32.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 9/9/20 12:02 PM, Bruce Ashfield wrote:
On Tue, Sep 8, 2020 at 8:23 AM Bruce Ashfield via
lists.yoctoproject.org
wrote:
On Tue, Sep 8, 2020 at 5:15 AM Xu, Yanfei wrote:
On 9/8/20 10:26 AM, Xu, Yanfei wrote:
On 9/8/20 10:01 AM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 11:43 AM
On 9/9/20 12:02 PM, Bruce Ashfield wrote:
On Tue, Sep 8, 2020 at 8:23 AM Bruce Ashfield via
lists.yoctoproject.org
wrote:
On Tue, Sep 8, 2020 at 5:15 AM Xu, Yanfei wrote:
On 9/8/20 10:26 AM, Xu, Yanfei wrote:
On 9/8/20 10:01 AM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 11:43 AM
On 9/8/20 10:26 AM, Xu, Yanfei wrote:
On 9/8/20 10:01 AM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 11:43 AM Xu, Yanfei
wrote:
On 9/7/20 7:53 PM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 5:56 AM Xu, Yanfei
wrote:
Hi Bruce,
When I excuted "make -C /usr/src/kernel sc
On 9/7/20 10:42 PM, Xu, Yanfei wrote:
On 9/7/20 7:53 PM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 5:56 AM Xu, Yanfei
wrote:
Hi Bruce,
When I excuted "make -C /usr/src/kernel scripts prepare" on target
mechine, I will be asked for choicing if to enable "GCC_PLU
On 9/7/20 7:53 PM, Bruce Ashfield wrote:
On Mon, Sep 7, 2020 at 5:56 AM Xu, Yanfei wrote:
Hi Bruce,
When I excuted "make -C /usr/src/kernel scripts prepare" on target
mechine, I will be asked for choicing if to enable "GCC_PLUGINS" and
other configurations de
Hi Bruce,
When I excuted "make -C /usr/src/kernel scripts prepare" on target
mechine, I will be asked for choicing if to enable "GCC_PLUGINS" and
other configurations depend on "GCC_PLUGINS" (The .config file doesn't
contain 'GCC_PLUGINS is not set')
But there were never be asked for these
Hi Bruce,
When I excuted "make -C /usr/src/kernel scripts prepare" on target
mechine, I will be asked for choicing if to enable "GCC_PLUGINS" and
other configurations depend on "GCC_PLUGINS" (The .config file didn,t
contain 'GCC_PLUGINS is not set')
But there were never be asked for these
From: Jiping Ma
arch/arm64/kernel/perf_callchain.c:107:6: warning: cast from
pointer to integer of different size [-Wpointer-to-int-cast]
if ((u32)tail + 4 >= buftail.fp)
^
arch/arm64/kernel/perf_callchain.c:110:9: warning: cast to
pointer from integer of different size
From: Yanfei Xu
Hi Bruce,
This patch fix compiling warnings which are introduced by an previous
patch. It should merge to both [linux-yocto-dev standard/base] and
[linux-yocto v5.4/standard/base]
From: Fang Jia
This change is for arm64 platform compat mode.
The change for arm32 platform has been included in this commit "perf: fix
backtrace for AAPCS with FP enabled".
This change replaces code designed for the obsolete ARM APCS ABI, which
causes failures of the perf backtrace logic
From: Yanfei Xu
Hi Bruce,
This patch should be merged to [linux-yocto-dev standard/base] and
[linux-yocto v5.4/standard/base]
V1-->V2
1.send this patch to linux-yocto and linux-yocto-dev instead of
cache repo.
Best regards,
Yanfei
Fang Jia (1):
arm64/perf: fix backtrace
No, you didn't miss any things. I just know that the patches are
generated from your scripts. And I will resend the patch against
linux-yocto.
Yanfei
On 5/2/20 11:19 PM, Bruce Ashfield wrote:
Did I miss applying this to the kernel-cache previously ? or did
I miss a patch against the
From: Yanfei Xu
This change is for arm64 platform compat mode.
--[cut here: not apply patch]
Samples: 119K of event 'cycles'
Event count (approx.): 114092698680
Children Self CommandShared Object Symbol
. ..
From: Yanfei Xu
Before the last commit, it updated the power-domain cells to 2.
However, the last commit added some codes without right power-domain
cells.
So, update OSPI power domain cells to 2 here to avoid warning when
compile dts.
Signed-off-by: Yanfei Xu
---
On 4/1/20 8:37 PM, Bruce Ashfield wrote:
On Tue, Mar 31, 2020 at 11:07 PM Xu, Yanfei wrote:
Hi Bruce,
Not a build failure, but a compile warning. when I built
v5.4/standard/xilinx-zynq kernel, It
occured the blow warning in log.do_compile.
# work-shared/xilinx-zynq/kernel-source/fs/yaffs2
Hi Bruce,
Not a build failure, but a compile warning. when I built
v5.4/standard/xilinx-zynq kernel, It
occured the blow warning in log.do_compile.
/# work-shared/xilinx-zynq/kernel-source/fs/yaffs2/yaffs_vfs.c:1829:6:
warning: unused variable 'i_version' //[-Wunused-variable]/
/# 1829 |
From: Yanfei Xu
Signed-off-by: Yanfei Xu
---
fs/yaffs2/yaffs_vfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 4fbd0a42ff3d..7a951baaf043 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1826,7
From: Yanfei Xu
CONFIG_NETDEVICES is set twice, remove one of them.
Signed-off-by: Yanfei Xu
---
bsp/ti-am65x/ti-am65x.cfg | 1 -
1 file changed, 1 deletion(-)
diff --git a/bsp/ti-am65x/ti-am65x.cfg b/bsp/ti-am65x/ti-am65x.cfg
index ec680ebe..008d388b 100644
--- a/bsp/ti-am65x/ti-am65x.cfg
From: Yanfei Xu
drop TI_DAVINCI_CPDMA option removed from v5.2 kernel
https://github.com/torvalds/linux/commit/99f629718272974405e8d180d2fa70c03c06d61f
drop SND_DAVINCI_SOC_MCASP option removed from v5.0 kernel
https://github.com/torvalds/linux/commit/f2055e145f2975a75dace8e386fad9364828cdb4
On 3/20/20 6:48 AM, Bruce Ashfield wrote:
On Wed, Mar 18, 2020 at 11:44 PM wrote:
From: Yanfei Xu
Before the last commit, it updated the power-domain cells to 2.
However, the last commit added some codes without right power-domain
cells.
So, update OSPI power domain cells to 2 here to avoid
From: Yanfei Xu
1)CONFIG_ENERGY_MODEL is a default configure items of arm64
defconfig.
Reference: https://patchwork.kernel.org/patch/10944391/
2)THERMAL_GOV_POWER_ALLOCATOR is set to y in nxp-ls20xx.cfg, but
from v5.5 kernel, the THERMAL_GOV_POWER_ALLOCATOR depends on
ENERGY_MODEL. So we enable
Hi Bruce,
I find PINCTRL_LYNXPOINT is actually removed from v5.6 kernel. And v5.4
kernel
is still using GPIO_LYNXPOINT.
Would you please revert it on v5.4 kernel-cache?
Reference:
https://github.com/torvalds/linux/commit/eb83479e18999e34b3b800f54aa31137f7f41c33
Thanks,
Yanfei
On 1/21/20
From: Yanfei Xu
Item CONFIG_CRYPTO_AES_X86_64 has been dropped from v5.4 kernel,
therefore, we drop it too.
Reference:
https://github.com/torvalds/linux/commit/1d2c3279311e4f03fcf164e1366f2fda9f4bfccf
Signed-off-by: Yanfei Xu
---
bsp/intel-x86/intel-x86-64.cfg | 1 -
1 file changed, 1
Hi Bruce,
Would you please help merge this patch to preempt branch? This compile
issue is a bit urgent.
Thanks!
Yanfei
On 3/12/20 12:57 AM, Xu, Yanfei wrote:
is From: Yanfei Xu
Hi Bruce,
v1--->v2
1. Add a if statement to separately operate the owner mem
From: Yanfei Xu
Hi Bruce,
v1--->v2
1. Add a if statement to separately operate the owner member
between standard and RT kernel.
Also I have completed the smoke test about aufs before this email.
Yanfei Xu (1):
aufs5:fix:avoid to access rw_sem.owner in RT kernel
From: Yanfei Xu
Fix build failure.
owner member is now made a permanent member of the rw_semaphore in
v5.6 kernel(commitid:c71fd893f). But the rw_semaphore in RT kernel
had been implemented with rt_mutex in rwsem-rt.h. Add if statment
to distinguish the two cases.
-Error
On 3/11/20 12:14 PM, He Zhe wrote:
On 3/10/20 2:50 PM, Xu, Yanfei wrote:
From: Yanfei Xu
Fix build failure.
Even though owner member is now made a permanent member of the
rw_semaphore. The rw_semaphore in rwsem-rt.h doesn't have owner
field still.
-Error messages
From: Yanfei Xu
Fix build failure.
Even though owner member is now made a permanent member of the
rw_semaphore. The rw_semaphore in rwsem-rt.h doesn't have owner
field still.
-Error messages-
|
Thanks for your imformation. I have tested it that apply this
commit to linux-yocto-dev and it works well.
Will you apply it to linux-yocto-dev too?
Regards,
//Yanfei
On 3/4/20 12:01 AM, Bruce Ashfield wrote:
On Tue, Mar 3, 2020 at 10:30 AM Xu, Yanfei wrote:
OK！ So If I understand correctly
OK！ So If I understand correctly, this failure will disappear after you
bring
the Makefile patch to linux-yocto recently？
Regards，
Yanfei
On 3/3/20 10:09 PM, Bruce Ashfield wrote:
On Tue, Mar 3, 2020 at 5:44 AM Xu, Yanfei wrote:
Hi Bruce,
Do you still remember this issue about vDSO
Hi Bruce,
Do you still remember this issue about vDSO of mips boot failure.The
linux-yocto-dev
still have this problem, even though the mips kernel have some fixes
after that.
Any new progress in it？
Regards，
Yanfei
On 3/3/20 5:28 PM, He Zhe wrote:
FYI
Forwarded Message
From: Yanfei Xu
When some layer include the edac feature and bitbake kernel ARCH
=mips, that will cause some warning masseges.
CONFIG_EDAC and CONFIG_EDAC_DEBUG depend on CONFIG_EDAC_SUPPORT,
but CONFIG_EDAC_SUPPORT isn't enabled in most of mips boards(except
CAVIUM_OCTEON_SOC, and edgerouter
On 12/3/19 11:14 PM, Bruce Ashfield wrote:
On Tue, Dec 3, 2019 at 4:38 AM Xu, Yanfei wrote:
On 12/2/19 12:28 PM, Bruce Ashfield wrote:
In message: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features:
avoid enabling edac feature in mips
on 27/11/2019 yanfei...@windriver.com
On 12/2/19 12:28 PM, Bruce Ashfield wrote:
In message: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features:
avoid enabling edac feature in mips
on 27/11/2019 yanfei...@windriver.com wrote:
From: Yanfei Xu
When some layer include this edac feature and bitbake kernel ARCH
52 matches
Mail list logo
