DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, david.marchand@6wind.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v4] eal: fix lib version for device generalization patches
Date: Sun, 06 Nov 2016 18:51:36 +0100	[thread overview]
Message-ID: <1715465.7F6udCOWBp@xps13> (raw)
In-Reply-To: <1477567752-23039-1-git-send-email-shreyansh.jain@nxp.com>

2016-10-27 16:59, Shreyansh Jain:
> rte_device/driver generalization patches [1] were merged without a change
> in the LIBABIVER variable. This patches bumps the macro of affected libs:
> 
> - libcryptodev and libetherdev have been bumped
> - librte_eal version changed in
>   d7e61ad3ae36 ("log: remove deprecated history dump")

Applied, thanks

  parent reply	other threads:[~2016-11-06 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 12:38 [dpdk-dev] [PATCH] eal: fix libabi macro " Shreyansh Jain
2016-10-26 13:00 ` [dpdk-dev] [PATCH v2] " Shreyansh Jain
2016-10-26 13:12   ` Shreyansh Jain
2016-10-26 14:25     ` Ferruh Yigit
2016-10-26 15:23       ` Thomas Monjalon
2016-10-27  5:07         ` Shreyansh Jain
2016-10-27  5:06       ` Shreyansh Jain
2016-10-27  7:08   ` [dpdk-dev] [PATCH v3] " Shreyansh Jain
2016-10-27 10:15     ` Thomas Monjalon
2016-10-27 11:10       ` Shreyansh Jain
2016-10-27 11:29     ` [dpdk-dev] [PATCH v4] eal: fix lib version " Shreyansh Jain
2016-10-27 11:32       ` Shreyansh Jain
2016-10-27 12:16         ` Thomas Monjalon
2016-11-06 17:51       ` Thomas Monjalon [this message]
2016-10-26 13:02 ` [dpdk-dev] [PATCH] eal: fix libabi macro " Shreyansh Jain

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=1715465.7F6udCOWBp@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shreyansh.jain@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).