From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [RFC PATCH 00/10] net: hns3: Adds support of debugfs to HNS3 driver Date: Sun, 11 Nov 2018 17:18:22 +0100 Message-ID: <20181111161822.GC15953@lunn.ch> References: <20181109220743.10264-1-salil.mehta@huawei.com> <20181109224346.GD5259@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "davem@davemloft.net" , "yuvalm@mellanox.com" , "leon@kernel.org" , "Zhuangyuzeng (Yisen)" , "lipeng (Y)" , "mehta.salil@opnsrc.net" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-rdma@vger.kernel.org" , Linuxarm To: Salil Mehta Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > 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