netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Wang Ming <machel@vivo.com>
Cc: Andy Gospodarek <andy@greyhouse.net>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	opensource.kernel@vivo.com
Subject: Re: [PATCH net v2] net: bonding: Remove error checking for debugfs_create_dir()
Date: Fri, 14 Jul 2023 09:12:22 -0700	[thread overview]
Message-ID: <3370.1689351142@famine> (raw)
In-Reply-To: <20230714090856.11571-1-machel@vivo.com>

Wang Ming <machel@vivo.com> wrote:

>It is expected that most callers should _ignore_ the errors
>return by debugfs_create_dir() in bond_debug_reregister().

	Why should the error be ignored?  It's not a fatal error, in the
sense that the bond itself should be unregistered, but I'm not sure why
an error message that the debugfs registration failed is undesirable.

	Also, the code in question is in bond_create_debugfs(), not
bond_debug_reregister().  The diff below looks a bit odd in that the
context line lists _reregister, but that's not the function being
changed.

	I thought the v1 patch was fine.

	-J

>Signed-off-by: Wang Ming <machel@vivo.com>
>---
> 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 594094526648..a41f765420dc 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
>

---
	-Jay Vosburgh, jay.vosburgh@canonical.com

  parent reply	other threads:[~2023-07-14 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  9:08 [PATCH net v2] net: bonding: Remove error checking for debugfs_create_dir() Wang Ming
2023-07-14 13:27 ` Markus Elfring
2023-07-14 16:12 ` Jay Vosburgh [this message]
2023-07-14 18:45   ` Markus Elfring
2023-07-17  8:49   ` 回复: " 王明-软件底层技术部

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=3370.1689351142@famine \
    --to=jay.vosburgh@canonical.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=machel@vivo.com \
    --cc=netdev@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).