DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Nipun Gupta <nipun.gupta@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] bus/fslmc: create function to prefetch next DQRR entry
Date: Wed, 31 Jan 2018 12:02:19 +0530	[thread overview]
Message-ID: <20180131063218.GA24795@jerin> (raw)
In-Reply-To: <AM2PR04MB0753A2A8E7EFE5AB46E8858B89E20@AM2PR04MB0753.eurprd04.prod.outlook.com>

-----Original Message-----
> Date: Wed, 24 Jan 2018 05:20:25 +0000
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> To: Nipun Gupta <nipun.gupta@nxp.com>, "jerin.jacob@caviumnetworks.com"
>  <jerin.jacob@caviumnetworks.com>
> CC: "dev@dpdk.org" <dev@dpdk.org>
> Subject: RE: [PATCH 1/3] bus/fslmc: create function to prefetch next DQRR
>  entry
> 
> > -----Original Message-----
> > From: Nipun Gupta [mailto:nipun.gupta@nxp.com]
> > Subject: [PATCH 1/3] bus/fslmc: create function to prefetch next DQRR
> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> > ---
> >  drivers/bus/fslmc/qbman/include/fsl_qbman_portal.h |  6 ++++++
> >  drivers/bus/fslmc/qbman/qbman_portal.c             | 11 +++++++++++
> >  drivers/bus/fslmc/rte_bus_fslmc_version.map        |  1 +
> >  3 files changed, 18 insertions(+)
> 
> Series
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied to dpdk-next-eventdev/master. Thanks.

      reply	other threads:[~2018-01-31  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 14:17 Nipun Gupta
2018-01-23 14:17 ` [dpdk-dev] [PATCH 2/3] event/dpaa2: prefetch the " Nipun Gupta
2018-01-23 14:17 ` [dpdk-dev] [PATCH 3/3] net/dpaa2: prefetch the annotation in event processing Nipun Gupta
2018-01-24  5:20 ` [dpdk-dev] [PATCH 1/3] bus/fslmc: create function to prefetch next DQRR entry Hemant Agrawal
2018-01-31  6:32   ` Jerin Jacob [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=20180131063218.GA24795@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@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).