scsi: ufs: qcom: Fix confusing cleanup.h syntax
Initializing automatic __free variables to NULL without need (e.g. branches with different allocations), followed by actual allocation is in contrary to explicit coding rules guiding cleanup.h: "Given that the "__free(...) = NULL" pattern for variables defined at the top of the function poses this potential interdependency problem the recommendation is to always define and assign variables in one statement and not group variable definitions at the top of the function when __free() is used." Code does not have a bug, but is less readable and uses discouraged coding practice, so fix that by moving declaration to the place of assignment. Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> Reviewed-by: Manivannan Sadhasivam <mani@kernel.org> Link: https://patch.msgid.link/20251208020807.5043-2-krzysztof.kozlowski@oss.qualcomm.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>master
parent
362432e9b9
commit
946574434a
|
|
@ -1769,10 +1769,9 @@ static void ufs_qcom_dump_testbus(struct ufs_hba *hba)
|
|||
{
|
||||
struct ufs_qcom_host *host = ufshcd_get_variant(hba);
|
||||
int i, j, nminor = 0, testbus_len = 0;
|
||||
u32 *testbus __free(kfree) = NULL;
|
||||
char *prefix;
|
||||
|
||||
testbus = kmalloc_array(256, sizeof(u32), GFP_KERNEL);
|
||||
u32 *testbus __free(kfree) = kmalloc_array(256, sizeof(u32), GFP_KERNEL);
|
||||
if (!testbus)
|
||||
return;
|
||||
|
||||
|
|
@ -1794,13 +1793,12 @@ static void ufs_qcom_dump_testbus(struct ufs_hba *hba)
|
|||
static int ufs_qcom_dump_regs(struct ufs_hba *hba, size_t offset, size_t len,
|
||||
const char *prefix, void __iomem *base)
|
||||
{
|
||||
u32 *regs __free(kfree) = NULL;
|
||||
size_t pos;
|
||||
|
||||
if (offset % 4 != 0 || len % 4 != 0)
|
||||
return -EINVAL;
|
||||
|
||||
regs = kzalloc(len, GFP_ATOMIC);
|
||||
u32 *regs __free(kfree) = kzalloc(len, GFP_ATOMIC);
|
||||
if (!regs)
|
||||
return -ENOMEM;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue