|
[PATCH v3 4.19.y-cip 15/17] spi: spi-mem: Fix a memory leak in spi_mem_dirmap_destroy()
From: Boris Brezillon <bbrezillon@...>
commit bfecfd6e23bf677c85828eb20fa4b13a18bffe23 upstream.
The dirmap descriptor object allocated in spi_mem_dirmap_create is
never freed. Add a
From: Boris Brezillon <bbrezillon@...>
commit bfecfd6e23bf677c85828eb20fa4b13a18bffe23 upstream.
The dirmap descriptor object allocated in spi_mem_dirmap_create is
never freed. Add a
|
By
Lad Prabhakar
·
#6015
·
|
|
[PATCH v3 4.19.y-cip 14/17] spi: spi-mem: Fix spi_mem_dirmap_destroy() kerneldoc
From: Boris Brezillon <bbrezillon@...>
commit 5c0c4ec9ba61a98ecb79036afc013bba8d5b85e3 upstream.
spi_mem_dirmap_destroy() takes a single argument, remove the @info entry
in the doc.
Fixes:
From: Boris Brezillon <bbrezillon@...>
commit 5c0c4ec9ba61a98ecb79036afc013bba8d5b85e3 upstream.
spi_mem_dirmap_destroy() takes a single argument, remove the @info entry
in the doc.
Fixes:
|
By
Lad Prabhakar
·
#6014
·
|
|
[PATCH v3 4.19.y-cip 13/17] spi: spi-mem: Add a new API to support direct mapping
From: Boris Brezillon <boris.brezillon@...>
commit aa167f3fed0c37e0e4c707d4331d827661f46644 upstream.
Most modern SPI controllers can directly map a SPI memory (or a portion
of the SPI
From: Boris Brezillon <boris.brezillon@...>
commit aa167f3fed0c37e0e4c707d4331d827661f46644 upstream.
Most modern SPI controllers can directly map a SPI memory (or a portion
of the SPI
|
By
Lad Prabhakar
·
#6013
·
|
|
[PATCH v3 4.19.y-cip 12/17] spi: spi-mem: Compute length only when needed
From: Tudor Ambarus <tudor.ambarus@...>
commit c0e035ac56680e74b27fc218c07e70f4b9b8b7a5 upstream.
When adjust_op_size is defined, len is never used. Move the len
computation where it's
From: Tudor Ambarus <tudor.ambarus@...>
commit c0e035ac56680e74b27fc218c07e70f4b9b8b7a5 upstream.
When adjust_op_size is defined, len is never used. Move the len
computation where it's
|
By
Lad Prabhakar
·
#6012
·
|
|
[PATCH v3 4.19.y-cip 11/17] spi: spi-mem: Fix passing zero to 'PTR_ERR' warning
From: YueHaibing <yuehaibing@...>
commit a9c52d42814a44472fe1205775320ec20f556908 upstream.
Fix smatch warning:
drivers/spi/spi-mem.c:746 spi_mem_probe() warn: passing zero to
From: YueHaibing <yuehaibing@...>
commit a9c52d42814a44472fe1205775320ec20f556908 upstream.
Fix smatch warning:
drivers/spi/spi-mem.c:746 spi_mem_probe() warn: passing zero to
|
By
Lad Prabhakar
·
#6011
·
|
|
[PATCH v3 4.19.y-cip 10/17] spi: spi-mem: fix reference leak in spi_mem_access_start
From: Zhang Qilong <zhangqilong3@...>
commit c02bb16b0e826bf0e19aa42c3ae60ea339f32cf5 upstream.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to
From: Zhang Qilong <zhangqilong3@...>
commit c02bb16b0e826bf0e19aa42c3ae60ea339f32cf5 upstream.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to
|
By
Lad Prabhakar
·
#6010
·
|
|
[PATCH v3 4.19.y-cip 09/17] spi: spi-mem: Split spi_mem_exec_op() code
From: Boris Brezillon <boris.brezillon@...>
commit f86c24f4795303e4024bc113196de32782f6ccb5 upstream.
The logic surrounding the ->exec_op() call applies to direct mapping
accessors. Move
From: Boris Brezillon <boris.brezillon@...>
commit f86c24f4795303e4024bc113196de32782f6ccb5 upstream.
The logic surrounding the ->exec_op() call applies to direct mapping
accessors. Move
|
By
Lad Prabhakar
·
#6009
·
|
|
[PATCH v3 4.19.y-cip 08/17] spi: spi-mem: export spi_mem_default_supports_op()
From: Naga Sureshkumar Relli <naga.sureshkumar.relli@...>
commit 46109648052fe778c75f199d72255c899578d6f7 upstream.
Export spi_mem_default_supports_op(), so that controller drivers
can use
From: Naga Sureshkumar Relli <naga.sureshkumar.relli@...>
commit 46109648052fe778c75f199d72255c899578d6f7 upstream.
Export spi_mem_default_supports_op(), so that controller drivers
can use
|
By
Lad Prabhakar
·
#6008
·
|
|
[PATCH v3 4.19.y-cip 07/17] spi: spi-mem: Add SPI_MEM_NO_DATA to the spi_mem_data_dir enum
From: Boris Brezillon <boris.brezillon@...>
commit 0ebb261a0b2d090de618a383d2378d4a00834958 upstream.
When defining spi_mem_op templates we don't necessarily know the size
that will be
From: Boris Brezillon <boris.brezillon@...>
commit 0ebb261a0b2d090de618a383d2378d4a00834958 upstream.
When defining spi_mem_op templates we don't necessarily know the size
that will be
|
By
Lad Prabhakar
·
#6007
·
|
|
[PATCH v3 4.19.y-cip 06/17] memory: renesas-rpc-if: Make rpcif_enable/disable_rpm() as static inline
commit 7889a7da59e0131ac60b858c73a3604ef88b1d96 upstream.
Define rpcif_enable_rpm() and rpcif_disable_rpm() as static
inline in the header instead of exporting them.
Suggested-by: Pavel Machek
commit 7889a7da59e0131ac60b858c73a3604ef88b1d96 upstream.
Define rpcif_enable_rpm() and rpcif_disable_rpm() as static
inline in the header instead of exporting them.
Suggested-by: Pavel Machek
|
By
Lad Prabhakar
·
#6006
·
|
|
[PATCH v3 4.19.y-cip 05/17] memory: renesas-rpc-if: Fix a node reference leak in rpcif_probe()
commit 4e6b86b409f9fc63fedb39d6e3a0202c4b0244ce upstream.
Release the node reference by calling of_node_put(flash) in the probe.
Fixes: ca7d8b980b67f ("memory: add Renesas RPC-IF
commit 4e6b86b409f9fc63fedb39d6e3a0202c4b0244ce upstream.
Release the node reference by calling of_node_put(flash) in the probe.
Fixes: ca7d8b980b67f ("memory: add Renesas RPC-IF
|
By
Lad Prabhakar
·
#6005
·
|
|
[PATCH v3 4.19.y-cip 04/17] memory: renesas-rpc-if: Fix unbalanced pm_runtime_enable in rpcif_{enable,disable}_rpm
commit 61a6d854b9555b420fbfae62ef26baa8b9493b32 upstream.
rpcif_enable_rpm calls pm_runtime_enable, so rpcif_disable_rpm needs to
call pm_runtime_disable and not pm_runtime_put_sync.
Fixes:
commit 61a6d854b9555b420fbfae62ef26baa8b9493b32 upstream.
rpcif_enable_rpm calls pm_runtime_enable, so rpcif_disable_rpm needs to
call pm_runtime_disable and not pm_runtime_put_sync.
Fixes:
|
By
Lad Prabhakar
·
#6004
·
|
|
[PATCH v3 4.19.y-cip 03/17] memory: renesas-rpc-if: Return correct value to the caller of rpcif_manual_xfer()
commit a0453f4ed066cae651b3119ed11f52d31dae1eca upstream.
In the error path of rpcif_manual_xfer() the value of ret is overwritten
by value returned by reset_control_reset() function and thus
commit a0453f4ed066cae651b3119ed11f52d31dae1eca upstream.
In the error path of rpcif_manual_xfer() the value of ret is overwritten
by value returned by reset_control_reset() function and thus
|
By
Lad Prabhakar
·
#6003
·
|
|
[PATCH v3 4.19.y-cip 02/17] memory: add Renesas RPC-IF driver
From: Sergei Shtylyov <sergei.shtylyov@...>
commit ca7d8b980b67f133317525c4273e144116ee1ae5 upstream.
Add the memory driver for Renesas RPC-IF which registers either SPI or
HyperFLash
From: Sergei Shtylyov <sergei.shtylyov@...>
commit ca7d8b980b67f133317525c4273e144116ee1ae5 upstream.
Add the memory driver for Renesas RPC-IF which registers either SPI or
HyperFLash
|
By
Lad Prabhakar
·
#6002
·
|
|
[PATCH v3 4.19.y-cip 01/17] dt-bindings: memory: document Renesas RPC-IF bindings
From: Sergei Shtylyov <sergei.shtylyov@...>
commit ab1c362061d92556bd96fd2c0b188f8e4223e3e3 upstream.
Renesas Reduced Pin Count Interface (RPC-IF) allows a SPI flash or
HyperFlash
From: Sergei Shtylyov <sergei.shtylyov@...>
commit ab1c362061d92556bd96fd2c0b188f8e4223e3e3 upstream.
Renesas Reduced Pin Count Interface (RPC-IF) allows a SPI flash or
HyperFlash
|
By
Lad Prabhakar
·
#6001
·
|
|
[PATCH v3 4.19.y-cip 00/17] Add Renesas RPC-IF driver
Hi Nobuhiro, Pavel,
This patch series adds SPI driver for the Renesas RPC-IF.
Alongside relevant changes for spi-mem have been also backported.
This enables accessing SPI flash chip connected to
Hi Nobuhiro, Pavel,
This patch series adds SPI driver for the Renesas RPC-IF.
Alongside relevant changes for spi-mem have been also backported.
This enables accessing SPI flash chip connected to
|
By
Lad Prabhakar
·
#6000
·
|
|
cip/linux-4.19.y-cip baseline: 239 runs, 6 regressions (v4.19.163-cip40-5-g95fea62f9f453)
cip/linux-4.19.y-cip baseline: 239 runs, 6 regressions (v4.19.163-cip40-5-g95fea62f9f453)
Regressions Summary
-------------------
platform | arch | lab | compiler |
cip/linux-4.19.y-cip baseline: 239 runs, 6 regressions (v4.19.163-cip40-5-g95fea62f9f453)
Regressions Summary
-------------------
platform | arch | lab | compiler |
|
By
kernelci.org bot <bot@...>
·
#5999
·
|
|
cip/linux-4.19.y-cip build: 130 builds: 0 failed, 130 passed, 48 warnings (v4.19.163-cip40-5-g95fea62f9f453)
cip/linux-4.19.y-cip build: 130 builds: 0 failed, 130 passed, 48 warnings (v4.19.163-cip40-5-g95fea62f9f453)
Full Build Summary:
cip/linux-4.19.y-cip build: 130 builds: 0 failed, 130 passed, 48 warnings (v4.19.163-cip40-5-g95fea62f9f453)
Full Build Summary:
|
By
kernelci.org bot <bot@...>
·
#5998
·
|
|
Re: [PATCH 4.19.y-cip] dt-bindings: thermal: rcar-gen3-thermal: Add r8a774e1 support
Hi!
I applied your recent patches, and pushed the result out:
95fea62f9f4534c3b963acd44f03754d9fe0829a dt-bindings: thermal: rcar-gen3-thermal: Add r8a774e1
Hi!
I applied your recent patches, and pushed the result out:
95fea62f9f4534c3b963acd44f03754d9fe0829a dt-bindings: thermal: rcar-gen3-thermal: Add r8a774e1
|
By
Pavel Machek
·
#5997
·
|
|
GitLab Merge Requests not working
Hi,
When I try to submit a MR on
https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec, I get:
500
Whoops, something went wrong on our end.
Try refreshing the page, or going back and
Hi,
When I try to submit a MR on
https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec, I get:
500
Whoops, something went wrong on our end.
Try refreshing the page, or going back and
|
By
Jonathan Sambrook
·
#5996
·
|