From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [PATCH] bus/fslmc: add support for scanned device count
Date: Fri, 12 Jan 2018 15:09:45 +0100 [thread overview]
Message-ID: <2335338.cbEazGGZus@xps> (raw)
In-Reply-To: <VI1PR0401MB24641D5D4024A9D4AA7F9D0C90170@VI1PR0401MB2464.eurprd04.prod.outlook.com>
12/01/2018 13:59, Shreyansh Jain:
> > -----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.
I have delegated the patch to Ferruh.
Thanks
next prev parent reply other threads:[~2018-01-12 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 13:08 [PATCH] bus/fslmc: add support for scanned device count Shreyansh Jain
2018-01-11 8:56 ` Hemant Agrawal
2018-01-12 11:45 ` Thomas Monjalon
2018-01-12 12:59 ` Shreyansh Jain
2018-01-12 14:09 ` Thomas Monjalon [this message]
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=2335338.cbEazGGZus@xps \
--to=thomas@monjalon.net \
--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 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.