DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/3] net/thunderx: fix build issues with 32bit target
Date: Mon, 20 Mar 2017 12:21:07 +0000	[thread overview]
Message-ID: <52ceaf2c-f19c-d999-4ac3-580338767eb7@intel.com> (raw)
In-Reply-To: <1489934928-27131-1-git-send-email-jerin.jacob@caviumnetworks.com>

On 3/19/2017 2:48 PM, Jerin Jacob wrote:
> Fixes: e438796617dc ("net/thunderx: add PMD skeleton")
> 
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

Series applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2017-03-20 12:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 15:39 [dpdk-dev] [PATCH 1/2] " Jerin Jacob
2017-03-10 15:39 ` [dpdk-dev] [PATCH 2/2] config: enable the thunderx nicvf driver Jerin Jacob
2017-03-12 14:02 ` [dpdk-dev] [PATCH v2 1/3] net/thunderx: fix build issues with 32bit target Jerin Jacob
2017-03-12 14:02   ` [dpdk-dev] [PATCH v2 2/3] net/thunderx: fix build issues with FreeBSD target Jerin Jacob
2017-03-12 14:02   ` [dpdk-dev] [PATCH v2 3/3] config: enable the thunderx nicvf driver Jerin Jacob
2017-03-19 14:48   ` [dpdk-dev] [PATCH v3 1/3] net/thunderx: fix build issues with 32bit target Jerin Jacob
2017-03-19 14:48     ` [dpdk-dev] [PATCH v3 2/3] net/thunderx: fix build issues with FreeBSD target Jerin Jacob
2017-03-19 14:48     ` [dpdk-dev] [PATCH v3 3/3] config: enable the thunderx nicvf driver Jerin Jacob
2017-03-20 12:21       ` Ferruh Yigit
2017-03-20 12:21     ` Ferruh Yigit [this message]
2017-03-15 16:32 ` [dpdk-dev] [PATCH 1/2] net/thunderx: fix build issues with 32bit target 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=52ceaf2c-f19c-d999-4ac3-580338767eb7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@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).