From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: add support for scanned device count
Date: Fri, 12 Jan 2018 12:59:10 +0000 [thread overview]
Message-ID: <VI1PR0401MB24641D5D4024A9D4AA7F9D0C90170@VI1PR0401MB2464.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1530347.4gd1k8lWyn@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, January 12, 2018 5:15 PM
> To: Shreyansh Jain <shreyansh.jain@nxp.com>
> Cc: dev@dpdk.org; ferruh.yigit@intel.com
> Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: add support for scanned device
> count
>
> 02/01/2018 14:08, Shreyansh Jain:
> > 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.
>
> Why is it based on next-net tree?
Because there is a dependency of a lot of patches for DPAA2 which were only on net-next when I sent this patch out. (dependency for lines, not for logic). Else, those would have conflicted when you would have merged net-next into master.
If those have been merged into master, this should be applicable on master as well.
next prev parent reply other threads:[~2018-01-12 12:59 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
2018-01-12 11:45 ` Thomas Monjalon
2018-01-12 12:59 ` Shreyansh Jain [this message]
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=VI1PR0401MB24641D5D4024A9D4AA7F9D0C90170@VI1PR0401MB2464.eurprd04.prod.outlook.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 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).