It is expected that most callers should _ignore_ the errors
return by debugfs_create_dir() in bond_debug_reregister().
Signed-off-by: Wang Ming <[email protected]>
---
drivers/net/bonding/bond_debugfs.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/bonding/bond_debugfs.c b/drivers/net/bonding/bond_debugfs.c
index 594094526..a41f76542 100644
--- a/drivers/net/bonding/bond_debugfs.c
+++ b/drivers/net/bonding/bond_debugfs.c
@@ -87,9 +87,6 @@ void bond_debug_reregister(struct bonding *bond)
void bond_create_debugfs(void)
{
bonding_debug_root = debugfs_create_dir("bonding", NULL);
-
- if (!bonding_debug_root)
- pr_warn("Warning: Cannot create bonding directory in debugfs\n");
}
void bond_destroy_debugfs(void)
--
2.25.1
On Wed, Jul 26, 2023 at 07:29:00PM +0800, Wang Ming wrote:
> It is expected that most callers should _ignore_ the errors
> return by debugfs_create_dir() in bond_debug_reregister().
>
> Signed-off-by: Wang Ming <[email protected]>
> ---
> drivers/net/bonding/bond_debugfs.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_debugfs.c b/drivers/net/bonding/bond_debugfs.c
> index 594094526..a41f76542 100644
> --- a/drivers/net/bonding/bond_debugfs.c
> +++ b/drivers/net/bonding/bond_debugfs.c
> @@ -87,9 +87,6 @@ void bond_debug_reregister(struct bonding *bond)
> void bond_create_debugfs(void)
> {
> bonding_debug_root = debugfs_create_dir("bonding", NULL);
> -
> - if (!bonding_debug_root)
> - pr_warn("Warning: Cannot create bonding directory in debugfs\n");
> }
>
> void bond_destroy_debugfs(void)
> --
> 2.25.1
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
On 7/26/23, Wang Ming <[email protected]> wrote:
> It is expected that most callers should _ignore_ the errors
> return by debugfs_create_dir() in bond_debug_reregister().
I'm confused; I recall that the prior version kept the pr_warn(), but
changed the
test from a NULL check to instead use IS_ERR(). I'll state again
that I think printing the error is useful, as it would provide an
indication of why the debugfs directory isn't available. I also don't
see an obvious way the error could be used to spam the dmesg.
-J
>
> Signed-off-by: Wang Ming <[email protected]>
> ---
> drivers/net/bonding/bond_debugfs.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_debugfs.c
> b/drivers/net/bonding/bond_debugfs.c
> index 594094526..a41f76542 100644
> --- a/drivers/net/bonding/bond_debugfs.c
> +++ b/drivers/net/bonding/bond_debugfs.c
> @@ -87,9 +87,6 @@ void bond_debug_reregister(struct bonding *bond)
> void bond_create_debugfs(void)
> {
> bonding_debug_root = debugfs_create_dir("bonding", NULL);
> -
> - if (!bonding_debug_root)
> - pr_warn("Warning: Cannot create bonding directory in debugfs\n");
> }
>
> void bond_destroy_debugfs(void)
> --
> 2.25.1
>
>