From: Richard Cochran <richardcochran@gmail.com>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>,
huangdaode <huangdaode@hisilicon.com>,
"lipeng (Y)" <lipeng321@huawei.com>,
"mehta.salil.lnk@gmail.com" <mehta.salil.lnk@gmail.com>,
"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 V3 net-next 5/8] net: hns3: Add support of TX Scheduler & Shaper to HNS3 driver
Date: Sun, 23 Jul 2017 08:13:32 +0200 [thread overview]
Message-ID: <20170723061332.wiubsmavqemcglmt@localhost.localdomain> (raw)
In-Reply-To: <F4CC6FACFEB3C54C9141D49AD221F7F93B81CCAF@FRAEML521-MBX.china.huawei.com>
On Sat, Jul 22, 2017 at 11:38:26PM +0000, Salil Mehta wrote:
> > On Sat, Jun 17, 2017 at 06:24:28PM +0100, Salil Mehta wrote:
> > > +
> > > +int hclge_tm_schd_init(struct hclge_dev *hdev);
> > > +int hclge_tm_setup_tc(struct hclge_dev *hdev);
> >
> > The definition of this function DNE.
> Sorry, I did not get what DNE means? Does Not Exist ?
> If yes, the I can see the definition of both the functions.
Where in this series is hclge_tm_setup_tc() defined?
Nowhere, AFAICT.
Thanks,
Richard
next prev parent reply other threads:[~2017-07-23 6:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 17:24 [PATCH V3 net-next 0/8] Hisilicon Network Subsystem 3 Ethernet Driver Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 1/8] net: hns3: Add support of HNS3 Ethernet Driver for hip08 SoC Salil Mehta
2017-06-17 17:54 ` Andrew Lunn
2017-07-22 23:17 ` Salil Mehta
2017-06-17 19:41 ` Andrew Lunn
2017-06-19 0:18 ` Bo Yu
2017-07-22 23:34 ` Salil Mehta
2017-06-19 0:57 ` Bo Yu
2017-07-22 23:39 ` Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 2/8] net: hns3: Add support of the HNAE3 framework Salil Mehta
2017-06-17 19:45 ` Andrew Lunn
2017-07-22 23:30 ` Salil Mehta
2017-06-18 15:02 ` Andrew Lunn
2017-07-22 23:32 ` Salil Mehta
2017-06-19 0:40 ` Bo Yu
2017-07-22 23:36 ` Salil Mehta
2017-06-19 16:59 ` Stephen Hemminger
2017-07-22 23:58 ` Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 3/8] net: hns3: Add HNS3 IMP(Integrated Mgmt Proc) Cmd Interface Support Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 4/8] net: hns3: Add HNS3 Acceleration Engine & Compatibility Layer Support Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 5/8] net: hns3: Add support of TX Scheduler & Shaper to HNS3 driver Salil Mehta
2017-06-18 16:45 ` Richard Cochran
2017-07-22 23:38 ` Salil Mehta
2017-07-23 6:13 ` Richard Cochran [this message]
2017-06-17 17:24 ` [PATCH V3 net-next 6/8] net: hns3: Add MDIO support to HNS3 Ethernet driver for hip08 SoC Salil Mehta
2017-06-19 3:52 ` Andrew Lunn
2017-07-22 23:53 ` Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 7/8] net: hns3: Add Ethtool support to HNS3 driver Salil Mehta
2017-06-17 17:24 ` [PATCH V3 net-next 8/8] net: hns3: Add HNS3 driver to kernel build framework & MAINTAINERS Salil Mehta
2017-06-18 6:07 ` [PATCH V3 net-next 0/8] Hisilicon Network Subsystem 3 Ethernet Driver Leon Romanovsky
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=20170723061332.wiubsmavqemcglmt@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=huangdaode@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=mehta.salil.lnk@gmail.com \
--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