firmware: tee_bnxt: Fix multiple call to tee_client_close_context
Subsystems (5)
PATCH v2 1/1 firmware: tee_bnxt: Fix multiple call to tee_client_close_context
Fix calling multiple tee_client_close_context in case of shm allocation fails.
--- drivers/firmware/broadcom/tee_bnxt_fw.c | 1 - 1 file changed, 1 deletion(-)
drivers/firmware/broadcom/tee_bnxt_fw.c +0 -1
@@ -215,7 +215,6 @@ static int tee_bnxt_fw_probe(struct device *dev) fw_shm_pool =tee_shm_alloc (pvt_data.ctx,MAX_SHM_MEM_SZ ,TEE_SHM_MAPPED |TEE_SHM_DMA_BUF );if (IS_ERR (fw_shm_pool)) { -tee_client_close_context (pvt_data.ctx);dev_err (pvt_data.dev,"tee_shm_alloc failed\n" ); err =PTR_ERR (fw_shm_pool); goto out_sess;
Signature · 1 line
2.7.4
PATCH v2 1/1 firmware: tee_bnxt: Reduce shm mem size to 4K
Reduce shm memory size as maximum size supported by optee_shm_register API is 4K.
--- drivers/firmware/broadcom/tee_bnxt_fw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/firmware/broadcom/tee_bnxt_fw.c +1 -1
@@ -12,7 +12,7 @@#include <linux/firmware/broadcom/tee_bnxt_fw.h> -#define MAX_SHM_MEM_SZ SZ_4M +#define MAX_SHM_MEM_SZ SZ_4K#define MAX_TEE_PARAM_ARRY_MEMB 4
Signature · 1 line
2.7.4
David Miller
maintainerWhat does "INTERNAL" mean in these patch Subject lines?
"INTERNAL" and version "v2" added accidently. Please ignore this. I`ll
send updated patch.
-----Original Message-----
From: David Miller [mailto:[email protected]]
Sent: Monday, January 06, 2020 4:18 AM
To: [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH INTERNAL v2] firmware: tee_bnxt: Fix multiple call to tee_client_close_context
What does "INTERNAL" mean in these patch Subject lines?