From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: netdev@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH v2 02/17] bonding: no need to print a message if debugfs_create_dir() fails
Date: Fri, 9 Aug 2019 14:30:53 +0200 [thread overview]
Message-ID: <20190809123108.27065-3-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20190809123108.27065-1-gregkh@linuxfoundation.org>
The debugfs core now will print a message if this function fails, so
don't duplicate that logic. Also, no need to change the code logic if
the call fails either, as no debugfs calls should interrupt normal
kernel code for any reason.
Cc: Jay Vosburgh <j.vosburgh@gmail.com>
Cc: Veaceslav Falico <vfalico@gmail.com>
Cc: Andy Gospodarek <andy@greyhouse.net>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/net/bonding/bond_debugfs.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/drivers/net/bonding/bond_debugfs.c b/drivers/net/bonding/bond_debugfs.c
index 1360f1ffe070..f3f86ef68ae0 100644
--- a/drivers/net/bonding/bond_debugfs.c
+++ b/drivers/net/bonding/bond_debugfs.c
@@ -55,11 +55,6 @@ void bond_debug_register(struct bonding *bond)
bond->debug_dir =
debugfs_create_dir(bond->dev->name, bonding_debug_root);
- if (!bond->debug_dir) {
- netdev_warn(bond->dev, "failed to register to debugfs\n");
- return;
- }
-
debugfs_create_file("rlb_hash_table", 0400, bond->debug_dir,
bond, &bond_debug_rlb_hash_fops);
}
--
2.22.0
next prev parent reply other threads:[~2019-08-09 12:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 12:30 [PATCH v2 00/17] Networking driver debugfs cleanups Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 01/17] wimax: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-08-09 12:30 ` Greg Kroah-Hartman [this message]
2019-08-09 12:30 ` [PATCH v2 03/17] mlx5: " Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 04/17] xgbe: " Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 05/17] bnxt: " Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 06/17] cxgb4: " Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 07/17] hns3: " Greg Kroah-Hartman
2019-08-09 12:30 ` [PATCH v2 08/17] nfp: " Greg Kroah-Hartman
2019-08-09 17:10 ` Jakub Kicinski
2019-08-09 12:31 ` [PATCH v2 09/17] stmmac: " Greg Kroah-Hartman
2019-08-09 12:31 ` [PATCH v2 10/17] dpaa2: " Greg Kroah-Hartman
2019-08-09 12:31 ` [PATCH v2 11/17] qca: " Greg Kroah-Hartman
2019-08-09 12:31 ` [PATCH v2 12/17] skge: " Greg Kroah-Hartman
2019-08-09 12:31 ` [PATCH v2 13/17] mvpp2: " Greg Kroah-Hartman
2019-08-09 12:31 ` [Intel-wired-lan] [PATCH v2 14/17] fm10k: " Greg Kroah-Hartman
2019-08-09 12:31 ` Greg Kroah-Hartman
2019-08-09 12:31 ` [Intel-wired-lan] [PATCH v2 15/17] i40e: " Greg Kroah-Hartman
2019-08-09 12:31 ` Greg Kroah-Hartman
2019-08-09 12:31 ` [Intel-wired-lan] [PATCH v2 16/17] ixgbe: " Greg Kroah-Hartman
2019-08-09 12:31 ` Greg Kroah-Hartman
2019-08-09 12:31 ` [PATCH v2 17/17] ieee802154: " Greg Kroah-Hartman
2019-08-09 12:34 ` Hennerich, Michael
2019-08-09 18:20 ` [PATCH v2 00/17] Networking driver debugfs cleanups David Miller
2019-08-10 10:17 ` Greg KH
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=20190809123108.27065-3-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.