From: Simon Horman <horms@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Rasesh Mody <rmody@marvell.com>,
Sudarsana Kalluru <skalluru@marvell.com>,
GR-Linux-NIC-Dev@marvell.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"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
Subject: Re: [PATCH v2 1/2] bna: Remove error checking for debugfs create APIs
Date: Sat, 26 Oct 2024 16:35:13 +0100 [thread overview]
Message-ID: <20241026153513.GI1507976@kernel.org> (raw)
In-Reply-To: <20241026034800.450-2-thunder.leizhen@huawei.com>
On Sat, Oct 26, 2024 at 11:47:59AM +0800, Zhen Lei wrote:
> Driver bna can work fine even if any previous call to debugfs create
> APIs failed. All return value checks of them should be dropped, as
> debugfs APIs say.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> drivers/net/ethernet/brocade/bna/bnad_debugfs.c | 15 +--------------
> 1 file changed, 1 insertion(+), 14 deletions(-)
>
> diff --git a/drivers/net/ethernet/brocade/bna/bnad_debugfs.c b/drivers/net/ethernet/brocade/bna/bnad_debugfs.c
> index 97291bfbeea589e..220d20a829c8a84 100644
> --- a/drivers/net/ethernet/brocade/bna/bnad_debugfs.c
> +++ b/drivers/net/ethernet/brocade/bna/bnad_debugfs.c
> @@ -500,19 +500,12 @@ bnad_debugfs_init(struct bnad *bnad)
> if (!bna_debugfs_root) {
> bna_debugfs_root = debugfs_create_dir("bna", NULL);
> atomic_set(&bna_debugfs_port_count, 0);
> - if (!bna_debugfs_root) {
> - netdev_warn(bnad->netdev,
> - "debugfs root dir creation failed\n");
> - return;
> - }
> }
>
> /* Setup the pci_dev debugfs directory for the port */
> snprintf(name, sizeof(name), "pci_dev:%s", pci_name(bnad->pcidev));
> if (!bnad->port_debugfs_root) {
> - bnad->port_debugfs_root =
> - debugfs_create_dir(name, bna_debugfs_root);
> -
> + bnad->port_debugfs_root = debugfs_create_dir(name, bna_debugfs_root);
nit: This change seems to only change line wrapping from <= 80 columns wide
(still preferred for Networking code) to > 80 columns wide (not so good).
Probably this part of the patch should be removed.
If not, reworked so it is <= 80 columns wide.
Otherwise, this patch looks good to me.
> atomic_inc(&bna_debugfs_port_count);
>
> for (i = 0; i < ARRAY_SIZE(bnad_debugfs_files); i++) {
> @@ -523,12 +516,6 @@ bnad_debugfs_init(struct bnad *bnad)
> bnad->port_debugfs_root,
> bnad,
> file->fops);
> - if (!bnad->bnad_dentry_files[i]) {
> - netdev_warn(bnad->netdev,
> - "create %s entry failed\n",
> - file->name);
> - return;
> - }
> }
> }
> }
--
pw-bot: changes-requested
next prev parent reply other threads:[~2024-10-26 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 3:47 [PATCH v2 0/2] bna: Remove error checking for debugfs create APIs Zhen Lei
2024-10-26 3:47 ` [PATCH v2 1/2] " Zhen Lei
2024-10-26 15:35 ` Simon Horman [this message]
2024-10-28 1:56 ` Leizhen (ThunderTown)
2024-10-26 3:48 ` [PATCH v2 2/2] bna: Remove field bnad_dentry_files[] in struct bnad Zhen Lei
2024-10-26 15:36 ` Simon Horman
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=20241026153513.GI1507976@kernel.org \
--to=horms@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmody@marvell.com \
--cc=skalluru@marvell.com \
--cc=thunder.leizhen@huawei.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.