From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: fix libabi macro for device generalization patches
Date: Thu, 27 Oct 2016 10:37:22 +0530 [thread overview]
Message-ID: <29852135-1e96-c0a6-ea19-a4adac3a9565@nxp.com> (raw)
In-Reply-To: <2105472.0JeDs3sFAP@xps13>
On Wednesday 26 October 2016 08:53 PM, Thomas Monjalon wrote:
> 2016-10-26 15:25, Ferruh Yigit:
>> eal version seems already increased for this release, 2 => 3, in:
>> d7e61ad3ae36 ("log: remove deprecated history dump")
>
> Yes thanks.
>
>> So NO need to increase it again, sorry for late notice, I just
>> recognized it.
>> Only librte_ether and librte_cryptodev requires the increase.
>
> Please could you also explain in the commit message that:
> - EAL was already bumped
> - what is the breakage in ethdev
> - what is the breakage in cryptodev
Indeed. Will do in v3
>
> Thanks
>
-
Shreyansh
next prev parent reply other threads:[~2016-10-27 5:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:38 [dpdk-dev] [PATCH] " 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 [this message]
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
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=29852135-1e96-c0a6-ea19-a4adac3a9565@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas.monjalon@6wind.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).