All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [PATCH] net/octeontx: use eventdev attributes to get count
Date: Tue, 10 Oct 2017 19:16:27 +0100	[thread overview]
Message-ID: <2de9c397-64a6-379c-395e-98ebcd6ba26e@intel.com> (raw)
In-Reply-To: <20171010180447.GA7725@jerin>

On 10/10/2017 7:04 PM, Jerin Jacob wrote:
> -----Original Message-----
>> Date: Tue, 10 Oct 2017 20:26:15 +0530
>> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>> To: ferruh.yigit@intel.com
>> CC: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>> Subject: [dpdk-dev] [PATCH] net/octeontx: use eventdev attributes to get
>>  count
>> X-Mailer: git-send-email 2.7.4
>>
>> Use the event device get attribute function to fetch the event
>> port and queue count
> 
> 
> Hi Ferruh, Thomas
> 
> The rte_event_queue_count()/rte_event_port_count() APIs are removed in
> next-eventdev. If next-eventdev changes first goes to master then next-net
> will have build issue. Request to squash this patch in next-next

Hi Jerin,

Thanks for heads up, I will get this into next-net before next-eventdev
merged into main repo.

Thanks,
ferruh

> 
> 
> 
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>

<...>

  reply	other threads:[~2017-10-10 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 14:56 [PATCH] net/octeontx: use eventdev attributes to get count Pavan Nikhilesh
2017-10-10 18:04 ` Jerin Jacob
2017-10-10 18:16   ` Ferruh Yigit [this message]
2017-10-10 19:38     ` Ferruh Yigit
2017-10-10 19:33 ` Ferruh Yigit
2017-10-11  1:20   ` Ferruh Yigit

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=2de9c397-64a6-379c-395e-98ebcd6ba26e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.