From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Minjie Du <duminjie@vivo.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"open list:INTEL IAA CRYPTO DRIVER"
<linux-crypto@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v1] crypto: iaa - Remove unnecessary debugfs_create_dir() error check in iaa_crypto_debugfs_init()
Date: Tue, 09 Jan 2024 10:25:21 -0600 [thread overview]
Message-ID: <30948df0bebe6d37d722b4ca4ab5feba7b7c0895.camel@linux.intel.com> (raw)
In-Reply-To: <20240109021916.20960-1-duminjie@vivo.com>
On Tue, 2024-01-09 at 10:19 +0800, Minjie Du wrote:
> This patch removes the debugfs_create_dir() error checking in
> iaa_crypto_debugfs_init(). Because the debugfs_create_dir() is
> developed
> in a way that the caller can safely handle the errors that
> occur during the creation of DebugFS nodes.
>
> Signed-off-by: Minjie Du <duminjie@vivo.com>
Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Thanks Minjie,
Tom
> ---
> drivers/crypto/intel/iaa/iaa_crypto_stats.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/crypto/intel/iaa/iaa_crypto_stats.c
> b/drivers/crypto/intel/iaa/iaa_crypto_stats.c
> index 2e3b7b73af20..cbf87d0effe3 100644
> --- a/drivers/crypto/intel/iaa/iaa_crypto_stats.c
> +++ b/drivers/crypto/intel/iaa/iaa_crypto_stats.c
> @@ -275,8 +275,6 @@ int __init iaa_crypto_debugfs_init(void)
> return -ENODEV;
>
> iaa_crypto_debugfs_root = debugfs_create_dir("iaa_crypto",
> NULL);
> - if (!iaa_crypto_debugfs_root)
> - return -ENOMEM;
>
> debugfs_create_u64("max_comp_delay_ns", 0644,
> iaa_crypto_debugfs_root,
> &max_comp_delay_ns);
next prev parent reply other threads:[~2024-01-09 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 2:19 [PATCH v1] crypto: iaa - Remove unnecessary debugfs_create_dir() error check in iaa_crypto_debugfs_init() Minjie Du
2024-01-09 16:25 ` Tom Zanussi [this message]
2024-01-26 9:01 ` Herbert Xu
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=30948df0bebe6d37d722b4ca4ab5feba7b7c0895.camel@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=davem@davemloft.net \
--cc=duminjie@vivo.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.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