From: Kai Ye <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wangzhou1@hisilicon.com>, <yekai13@huawei.com>
Subject: [PATCH v2 4/4] crypto: hisilicon/debugfs - delete redundant null assignment operations
Date: Sat, 5 Nov 2022 09:53:57 +0000 [thread overview]
Message-ID: <20221105095357.21199-5-yekai13@huawei.com> (raw)
In-Reply-To: <20221105095357.21199-1-yekai13@huawei.com>
There is no security data in the pointer. It is only a value transferred
as a structure. So not need to set the pointer to null.
Signed-off-by: Kai Ye <yekai13@huawei.com>
---
drivers/crypto/hisilicon/debugfs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/hisilicon/debugfs.c b/drivers/crypto/hisilicon/debugfs.c
index 9f1bfabd7ae2..bcd5cdaea736 100644
--- a/drivers/crypto/hisilicon/debugfs.c
+++ b/drivers/crypto/hisilicon/debugfs.c
@@ -822,7 +822,6 @@ static void dfx_regs_uninit(struct hisi_qm *qm,
dregs[i].regs = NULL;
}
kfree(dregs);
- dregs = NULL;
}
static struct dfx_diff_registers *dfx_regs_init(struct hisi_qm *qm,
--
2.17.1
prev parent reply other threads:[~2022-11-05 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 9:53 [PATCH v2 0/4] crypto: hisilicon/qm - reconstruct and optimize the debugfs code Kai Ye
2022-11-05 9:53 ` [PATCH v2 1/4] crypto: hisilicon/qm - modify the process of regs dfx Kai Ye
2022-11-05 10:18 ` Herbert Xu
2022-11-07 6:53 ` yekai (A)
2022-11-07 8:47 ` Herbert Xu
2022-11-07 10:46 ` yekai (A)
2022-11-05 9:53 ` [PATCH v2 2/4] crypto: hisilicon/qm - split a debugfs.c from qm Kai Ye
2022-11-05 9:53 ` [PATCH v2 3/4] crypto: hisilicon/qm - the command dump process is modified Kai Ye
2022-11-05 9:53 ` Kai Ye [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221105095357.21199-5-yekai13@huawei.com \
--to=yekai13@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox