[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <083ef067-b628-4dc9-a3e5-ccbb37de3976@lunn.ch>
Date: Fri, 11 Jul 2025 15:33:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Wei Fang <wei.fang@....com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
richardcochran@...il.com, claudiu.manoil@....com,
vladimir.oltean@....com, xiaoning.wang@....com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, fushi.peng@....com,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH net-next 06/12] ptp: netc: add debugfs support to loop
back pulse signal
> +static void netc_timer_create_debugfs(struct netc_timer *priv)
> +{
> + char debugfs_name[24];
> + struct dentry *root;
> +
> + snprintf(debugfs_name, sizeof(debugfs_name), "netc_timer%d",
> + priv->phc_index);
> + root = debugfs_create_dir(debugfs_name, NULL);
> + if (IS_ERR(root))
> + return;
You should never check the return values from a debugfs_
calls. debugfs is full optional, and the driver should work without
it. debugfs will also happily accept a NULL or error code as a
parameter. So even if debugfs_create_dir() fails, keep going,
debugfs_create_file() won't explode.
Andrew
Powered by blists - more mailing lists