[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200609111224.GA780233@kroah.com>
Date: Tue, 9 Jun 2020 13:12:24 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org, Joe Perches <joe@...ches.com>,
Jason Baron <jbaron@...mai.com>
Subject: Re: [PATCH v3 5/7] venus: Add debugfs interface to set firmware log
level
On Tue, Jun 09, 2020 at 01:46:02PM +0300, Stanimir Varbanov wrote:
> +int venus_dbgfs_init(struct venus_core *core)
> +{
> + core->root = debugfs_create_dir("venus", NULL);
> + if (IS_ERR(core->root))
> + return IS_ERR(core->root);
You really do not care, and obviously did not test this on a system with
CONFIG_DEBUG_FS disabled :)
Just make the call to debugfs, and move on, feed it into other debugfs
calls, all is good.
This function should just return 'void', no need to care about this at
all.
> + ret = venus_sys_set_debug(hdev, venus_fw_debug);
> + if (ret)
> + dev_warn(dev, "setting fw debug msg ON failed (%d)\n", ret);
Why do you care about this "error"?
thanks,
greg k-h
Powered by blists - more mailing lists