[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170610163535.GC26740@lunn.ch>
Date: Sat, 10 Jun 2017 18:35:35 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Mintz, Yuval" <Yuval.Mintz@...ium.com>
Cc: Salil Mehta <salil.mehta@...wei.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"yisen.zhuang@...wei.com" <yisen.zhuang@...wei.com>,
"huangdaode@...ilicon.com" <huangdaode@...ilicon.com>,
"lipeng321@...wei.com" <lipeng321@...wei.com>,
"mehta.salil.lnk@...il.com" <mehta.salil.lnk@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxarm@...wei.com" <linuxarm@...wei.com>
Subject: Re: [PATCH net-next 8/9] net: hns3: Add support of debugfs interface
to HNS3 driver
On Sat, Jun 10, 2017 at 12:51:57PM +0000, Mintz, Yuval wrote:
> > This adds the support of the debugfs interface to the driver for debugging
> > purposes.
>
> > +const struct hclge_support_cmd support_cmd[] = {
> > + {"send cmd", 8, hclge_dbg_send,
> > + "opcode flag data0 data1 data2 data3 data4 data5"},
> > + {"help", 4, hclge_dbg_usage, "no option"}, };
>
> Is there an actual description of what this does? Or is it simply a huge backdoor?
It looks like a huge backdoor to the chip.
It is O.K. to have such a patch internally for your own development
work, but it should not be submitted for mainline.
NACK
Andrew
Powered by blists - more mailing lists