All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Santosh Shukla <santosh.shukla@caviumnetworks.com>,
	dev@dpdk.org, olivier.matz@6wind.com, thomas@monjalon.net
Subject: Re: [PATCH v1 1/2] mempool/octeontx: move mbox from event to mempool
Date: Sat, 21 Oct 2017 15:21:01 +0530	[thread overview]
Message-ID: <20171021095100.GB14930@jerin> (raw)
In-Reply-To: <36f3ca70-b038-724a-1364-38f1d9455ea9@nxp.com>

-----Original Message-----
> Date: Tue, 17 Oct 2017 15:19:26 +0530
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> To: Santosh Shukla <santosh.shukla@caviumnetworks.com>, dev@dpdk.org
> CC: olivier.matz@6wind.com, thomas@monjalon.net,
>  jerin.jacob@caviumnetworks.com
> Subject: Re: [PATCH v1 1/2] mempool/octeontx: move mbox from event to
>  mempool
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
>  Thunderbird/45.8.0
> 
> Thanks! this patch solves the issue.
> 
> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Thomas,

Can you merge this patch to master if there are no more review comments?
NXP's Eventdev Rx adapter patch is blocked on this. I would like pull
NXP's Eventdev Rx adapter series for RC2(It has dependency on this series
to be in master)
http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=Nipun

  reply	other threads:[~2017-10-21  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 13:42 [PATCH v1 1/2] mempool/octeontx: move mbox from event to mempool Santosh Shukla
2017-10-16 13:42 ` [PATCH v1 2/2] event/octeontx: bump library version Santosh Shukla
2017-10-17  9:50   ` Hemant Agrawal
2017-10-23 14:38   ` Thomas Monjalon
2017-10-17  9:49 ` [PATCH v1 1/2] mempool/octeontx: move mbox from event to mempool Hemant Agrawal
2017-10-21  9:51   ` Jerin Jacob [this message]
2017-10-18  4:46 ` Pavan Nikhilesh Bhagavatula
2017-10-23 14:50 ` Thomas Monjalon

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=20171021095100.GB14930@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=olivier.matz@6wind.com \
    --cc=santosh.shukla@caviumnetworks.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 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.