[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 11 Nov 2018 17:18:22 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Salil Mehta <salil.mehta@...wei.com>
Cc: "davem@...emloft.net" <davem@...emloft.net>,
"yuvalm@...lanox.com" <yuvalm@...lanox.com>,
"leon@...nel.org" <leon@...nel.org>,
"Zhuangyuzeng (Yisen)" <yisen.zhuang@...wei.com>,
"lipeng (Y)" <lipeng321@...wei.com>,
"mehta.salil@...src.net" <mehta.salil@...src.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Linuxarm <linuxarm@...wei.com>
Subject: Re: [RFC PATCH 00/10] net: hns3: Adds support of debugfs to HNS3
driver
> Agreed. But what about if we want to expose anything related to
> firmware to user-space using the debugfs, assuming we are presenting
> information in structured way and not as a black-box to some user-space
> application. Is it something which might be discouraged?
Hi Salil
Please take a look at devlink. Mellonex have been adding commands to
it for dumping firmware states.
Andrew
Powered by blists - more mailing lists