Re: [PATCH 4/6] soc: qcom: smem: fix off-by-one error in qcom_smem_alloc_private()

On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote: > It's OK if the space for a newly-allocated uncached entry actually > touches the free cached space boundary. It's only a problem if it > would cross it. > > Signed-off-by: Alex Elder Reviewed-by: Bjorn Andersson

Re: [PATCH 4/6] soc: qcom: smem: fix off-by-one error in qcom_smem_alloc_private()

On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote: > It's OK if the space for a newly-allocated uncached entry actually > touches the free cached space boundary. It's only a problem if it > would cross it. > > Signed-off-by: Alex Elder Reviewed-by: Bjorn Andersson Regards, Bjorn > --- >

[PATCH 4/6] soc: qcom: smem: fix off-by-one error in qcom_smem_alloc_private()

It's OK if the space for a newly-allocated uncached entry actually touches the free cached space boundary. It's only a problem if it would cross it. Signed-off-by: Alex Elder --- drivers/soc/qcom/smem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/6] soc: qcom: smem: fix off-by-one error in qcom_smem_alloc_private()

It's OK if the space for a newly-allocated uncached entry actually touches the free cached space boundary. It's only a problem if it would cross it. Signed-off-by: Alex Elder --- drivers/soc/qcom/smem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/soc/qcom/smem.c