Re: [linux-yocto] [PATCH v5.2 rt] mmc: cavium-thunderx: Drop the IRQF_NO_THREAD constraint

2019-10-13 Thread Bruce Ashfield
In message: [PATCH v5.2 rt] mmc: cavium-thunderx: Drop the IRQF_NO_THREAD constraint on 10/10/2019 Kevin Hao wrote: > The IRQF_NO_THREAD is added by a Marvell SDK patch 238e623e1024 ("mmc: > cavium: fix swiotlb buffer is full") in order to get back some of the > performance loss. But in some

Re: [linux-yocto] [PATCH v5.2] tracing/arm64: Have max stack tracer handle the case of return address after data

2019-10-13 Thread Bruce Ashfield
merged Bruce In message: [PATCH v5.2] tracing/arm64: Have max stack tracer handle the case of return address after data on 10/10/2019 Kevin Hao wrote: > From: "Steven Rostedt (VMware)" > > commit f7edb451fa51e44e62177347ea7850aa0e901ea5 upstream > > Most archs (well at least x86) store the

Re: [linux-yocto] [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers

2019-10-13 Thread Bruce Ashfield
merged. Bruce In message: [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers on 09/10/2019 Kevin Hao wrote: > From: Masami Hiramatsu > > commit 760d8ed069c4e32a92e2ba251a3b0d9a87a3e771 upstream > > Remove rcu_read_lock()/rcu_read_unlock() from debug exception > handlers

Re: [linux-yocto] [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers

2019-10-13 Thread Bruce Ashfield
merged. Bruce In message: [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers on 09/10/2019 Kevin Hao wrote: > From: Masami Hiramatsu > > commit 760d8ed069c4e32a92e2ba251a3b0d9a87a3e771 upstream > > Remove rcu_read_lock()/rcu_read_unlock() from debug exception > handlers

Re: [yocto] [layerindex-web] [PATCH 0/3] Some misc changes/fixes..

2019-10-13 Thread Paul Eggleton
Hi Mark On Sunday, 13 October 2019 2:56:30 PM NZDT Mark Hatle wrote: > A few misc changes/fixes. The first two are well tested. However, I suspect > the 3/3 may be incorrect and I've labeled it an RFC due to this. > > 1/3 - '.' wasn't allowed in branch names w/o an error. This turned out >

Re: [yocto] [warrior 0/3] Pull request

2019-10-13 Thread akuster808
ping On 10/6/19 8:40 AM, Armin Kuster wrote: > Please merge these changes to meta-yocto warrior > > The following changes since commit c16082ffa61f485e120670fbdf075f3fa8597494: > > poky.conf: Bump version for 2.7.1 warrior release (2019-06-30 22:41:39 > +0100) > > are available in the git

Re: [yocto] [thud][PATCH] linux-yocto/4.14: meta-yocto-bsp update to 143

2019-10-13 Thread akuster
ping. On 10/9/19 8:09 AM, Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > .../recipes-kernel/linux/linux-yocto_4.14.bbappend | 20 > ++-- > 1 file changed, 10 insertions(+), 10 deletions(-) > > diff --git

[linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 1/2] i2c: cadence: do not clear bus_hold_flag in mrecv

2019-10-13 Thread quanyang.wang
From: Quanyang Wang When using i2c_smbus_read_byte_data to read one byte from a slave device, because of the commit d358def70688 ("i2c: cadence: Fix the hold bit setting"), the transaction becomes: S Addr Wr [A] Comm [A] P S Addr Rd [A] [Data] NA P ^

[linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 2/2] arch: arm64: dts: add overlay dts file

2019-10-13 Thread quanyang.wang
From: MengLi Add overlay dts file for updating FPGA bitstream file on zynqmp platform. Signed-off-by: Meng Li Signed-off-by: Quanyang Wang --- arch/arm64/boot/dts/xilinx/Makefile| 1 + .../dts/xilinx/zynqmp-zcu102-fpga-update.dts | 18 ++ 2 files changed, 19

[linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/2] patches for xilinx

2019-10-13 Thread quanyang.wang
From: Quanyang Wang Hi Bruce, Michal, The patch "arch: arm64: dts: add overlay dts file" is made for FPGA programming using Device Tree Overlay. The patch "i2c: cadence: do not clear bus_hold_flag in mrecv" is to fix a bug which is introduced by upstream commit d358def70688. This bug will

[yocto] download.yoctoproject.org - Certificate expired

2019-10-13 Thread Guilhem Saurel
Hi, The certificate installed on https://download.yoctoproject.org expired about 4 days ago. Is anyone else experiencing the same issue? Is a new certificate going to be installed ? Thanks, Guilhem. signature.asc Description: PGP signature -- ___