From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>, <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: add support for scanned device count
Date: Thu, 11 Jan 2018 14:26:51 +0530 [thread overview]
Message-ID: <98aa64e3-d12c-8dde-937c-3f309969439b@nxp.com> (raw)
In-Reply-To: <20180102130838.3630-1-shreyansh.jain@nxp.com>
On 1/2/2018 6:38 PM, Shreyansh Jain wrote:
> FSLMC bus detects a multiple type of logical objects representing
> components of the datapath.
>
> Using the type of device, a newly introduced API
> rte_fslmc_get_device_count can return the count of devices
> scanned of that device type.
>
> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> ---
> :: This patch is based on *net-next* tree.
<snip>..
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2018-01-11 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 13:08 Shreyansh Jain
2018-01-11 8:56 ` Hemant Agrawal [this message]
2018-01-12 11:45 ` Thomas Monjalon
2018-01-12 12:59 ` Shreyansh Jain
2018-01-12 14:09 ` Thomas Monjalon
2018-01-12 18:01 ` 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=98aa64e3-d12c-8dde-937c-3f309969439b@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shreyansh.jain@nxp.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).