DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Legacy, Allain" <Allain.Legacy@windriver.com>
To: santosh <santosh.shukla@caviumnetworks.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"Gaëtan Rivet" <gaetan.rivet@6wind.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "Zhang, Qing Long (Eric)" <Eric.Zhang@windriver.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Peters, Matt" <Matt.Peters@windriver.com>
Subject: Re: [dpdk-dev] [PATCH] eal: force IOVA mode to physical
Date: Thu, 30 Aug 2018 13:56:02 +0000	[thread overview]
Message-ID: <70A7408C6E1BFB41B192A929744D8523BABDEACD@ALA-MBD.corp.ad.wrs.com> (raw)
In-Reply-To: <a8b41461-9888-b88f-7b3b-1c5a4b225e37@caviumnetworks.com>

> -----Original Message-----
> From: santosh [mailto:santosh.shukla@caviumnetworks.com]
> Sent: Thursday, August 30, 2018 8:59 AM
> To: hemant.agrawal@nxp.com; Gaëtan Rivet; Burakov, Anatoly
> Cc: Zhang, Qing Long (Eric); bruce.richardson@intel.com; dev@dpdk.org;
> Legacy, Allain; Peters, Matt
> Subject: Re: [dpdk-dev] [PATCH] eal: force IOVA mode to physical
> 
> 
> On Thursday 30 August 2018 05:43 PM, Hemant wrote:
> > External Email
<...>
> 
> [1] http://patchwork.dpdk.org/patch/25192/

Is there a reason this was abandoned? 

  reply	other threads:[~2018-08-30 13:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 15:58 eric zhang
2018-08-30  6:13 ` Hemant
2018-08-30  9:09 ` Burakov, Anatoly
2018-08-30  9:43   ` Gaëtan Rivet
2018-08-30 12:13     ` Hemant
2018-08-30 12:59       ` santosh
2018-08-30 13:56         ` Legacy, Allain [this message]
2018-08-30 13:58           ` santosh
2018-09-05  3:40         ` Eric Zhang
2018-09-06  7:34           ` Jerin Jacob
2018-09-07  9:26             ` Burakov, Anatoly
2018-09-07 20:13               ` Eric Zhang
2018-09-11 17:21                 ` Eric Zhang
2018-09-17  8:32                   ` Stojaczyk, Dariusz
2018-09-17 19:04                     ` Eric Zhang

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=70A7408C6E1BFB41B192A929744D8523BABDEACD@ALA-MBD.corp.ad.wrs.com \
    --to=allain.legacy@windriver.com \
    --cc=Eric.Zhang@windriver.com \
    --cc=Matt.Peters@windriver.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=santosh.shukla@caviumnetworks.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).