From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>,
"lipeng (Y)" <lipeng321@huawei.com>,
"mehta.salil@opnsrc.net" <mehta.salil@opnsrc.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH net-next 0/8] net: hns3: Adds support of debugfs to HNS3 driver
Date: Wed, 21 Nov 2018 10:25:29 -0800 [thread overview]
Message-ID: <20181121102529.7d8df6e4@cakuba.netronome.com> (raw)
In-Reply-To: <F4CC6FACFEB3C54C9141D49AD221F7F93BFC8A64@FRAEML521-MBX.china.huawei.com>
On Wed, 21 Nov 2018 18:06:19 +0000, Salil Mehta wrote:
> > From: Jakub Kicinski [mailto:jakub.kicinski@netronome.com]
> > Sent: Monday, November 19, 2018 10:30 PM
> > To: Salil Mehta <salil.mehta@huawei.com>
> > Cc: davem@davemloft.net; Zhuangyuzeng (Yisen) <yisen.zhuang@huawei.com>;
> > lipeng (Y) <lipeng321@huawei.com>; mehta.salil@opnsrc.net;
> > netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> > <linuxarm@huawei.com>
> > Subject: Re: [PATCH net-next 0/8] net: hns3: Adds support of debugfs to
> > HNS3 driver
> >
> > On Mon, 19 Nov 2018 21:18:37 +0000, Salil Mehta wrote:
> > > This patchset adds support of debugfs to the HNS3 driver.
> > >
> > > Support has been added to query info related to below items:
> > > 1. Queue related
> > > 2. Flow Director
> > > 3. TC config
> > > 4. Transmit Module/Scheduler
> > > 5. QoS pause
> > > 6. QoS buffer
> > > 7. QoS prio map
> >
> > Please provide a more informative cover letter.
> >
> > From a short glance it looks like you add a single debugfs file, which
> > can be written to, and upon that write the driver will dump stuff into
> > kernel logs.
>
> That is correct. Do you foresee any problem with it or are we doing something
> which is objectionable?
Its fine with me, but I think not everyone reading the list will read
the code so a few extra words and adding one of the examples from the
patches to the cover letter could help people understand the changes.
prev parent reply other threads:[~2018-11-21 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:18 [PATCH net-next 0/8] net: hns3: Adds support of debugfs to HNS3 driver Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 1/8] net: hns3: Add debugfs framework registration Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 2/8] net: hns3: Add "queue info" query function Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 3/8] net: hns3: Add "FD flow table" info " Salil Mehta
2018-11-19 22:30 ` Jakub Kicinski
2018-11-21 16:25 ` Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 4/8] net: hns3: Add "tc config" " Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 5/8] net: hns3: Add "tm " Salil Mehta
2018-11-19 21:18 ` [PATCH net-next 6/8] net: hns3: Add pause config " Salil Mehta
2018-11-19 22:29 ` [PATCH net-next 0/8] net: hns3: Adds support of debugfs to HNS3 driver Jakub Kicinski
2018-11-21 18:06 ` Salil Mehta
2018-11-21 18:25 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181121102529.7d8df6e4@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=mehta.salil@opnsrc.net \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox