From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/octeontx: use eventdev attributes to get count
Date: Wed, 11 Oct 2017 02:20:40 +0100 [thread overview]
Message-ID: <ecdd072c-5e66-0583-0c52-c8bae568728d@intel.com> (raw)
In-Reply-To: <8df554e1-83b2-1fd2-c383-87bebb3faae4@intel.com>
On 10/10/2017 8:33 PM, Ferruh Yigit wrote:
> On 10/10/2017 3:56 PM, Pavan Nikhilesh wrote:
>> Use the event device get attribute function to fetch the event
>> port and queue count
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Squashed into relevant commit in next-net, thanks.
Commit: 485c30ac8c39 ("net/octeontx: add net device probe and remove")
prev parent reply other threads:[~2017-10-11 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:56 Pavan Nikhilesh
2017-10-10 18:04 ` Jerin Jacob
2017-10-10 18:16 ` Ferruh Yigit
2017-10-10 19:38 ` Ferruh Yigit
2017-10-10 19:33 ` Ferruh Yigit
2017-10-11 1:20 ` Ferruh Yigit [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=ecdd072c-5e66-0583-0c52-c8bae568728d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.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;
as well as URLs for NNTP newsgroup(s).