All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Rajesh Ravi <rajesh.ravi@broadcom.com>,
	David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Jonathan Richardson <jonathan.richardson@broadcom.com>,
	Scott Branden <scott.branden@broadcom.com>,
	Vikram Mysore Prakash <vikram.prakash@broadcom.com>,
	Srinath Mannam <srinath.mannam@broadcom.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 19.11] vfio: fix DMA mapping of externally allocated heaps
Date: Wed, 6 Nov 2019 16:03:33 +0000	[thread overview]
Message-ID: <1f5d875d-9f50-2f73-3721-d0bdc68a4393@intel.com> (raw)
In-Reply-To: <CAAr5zNebTYCVgHp_406ES8b--qqYg5SvTQ5DxW1sJfXQB8mVpA@mail.gmail.com>

On 06-Nov-19 3:27 PM, Rajesh Ravi wrote:
> Thanks Anatoly & David.
> The main patch provided  by Anatoly is not compatible with DPDK 19.02.
> So I had to make following patch and verified it to be working with DPDK 
> 19.02 & SPDK 19.07 combination.
> 

Hi Rajesh,

Thanks for testing. If your tests were successful, would you please 
respond with a Tested-by: to the patch you have tested?

-- 
Thanks,
Anatoly

  reply	other threads:[~2019-11-06 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 15:15 [dpdk-dev] [PATCH 19.11] vfio: fix DMA mapping of externally allocated heaps Anatoly Burakov
2019-11-05 17:15 ` Burakov, Anatoly
2019-11-06 13:58   ` David Marchand
2019-11-06 15:27     ` Rajesh Ravi
2019-11-06 16:03       ` Burakov, Anatoly [this message]
2019-11-06 21:53 ` David Marchand
2019-11-06 22:12   ` Thomas Monjalon
2019-11-07  6:35 ` Rajesh Ravi
2019-11-07 15:35 ` David Marchand

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=1f5d875d-9f50-2f73-3721-d0bdc68a4393@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jonathan.richardson@broadcom.com \
    --cc=rajesh.ravi@broadcom.com \
    --cc=scott.branden@broadcom.com \
    --cc=srinath.mannam@broadcom.com \
    --cc=thomas@monjalon.net \
    --cc=vikram.prakash@broadcom.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.