All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 12/13] ethdev: fix library version in meson build
Date: Thu, 5 Apr 2018 18:33:54 +0100	[thread overview]
Message-ID: <f59ee483-bf07-7f46-beca-29f1c9df7241@intel.com> (raw)
In-Reply-To: <20180323214637.GL19100@bricha3-MOBL.ger.corp.intel.com>

On 3/23/2018 9:46 PM, Bruce Richardson wrote:
> On Tue, Mar 20, 2018 at 11:26:26AM +0000, Andrew Rybchenko wrote:
>> Fixes: 701ac75666b9 ("ethdev: remove versioning of ethdev filter control function")
>>
>> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
>> ---
>>  lib/librte_ether/meson.build | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/librte_ether/meson.build b/lib/librte_ether/meson.build
>> index 7fed860..12bdb6b 100644
>> --- a/lib/librte_ether/meson.build
>> +++ b/lib/librte_ether/meson.build
>> @@ -2,7 +2,7 @@
>>  # Copyright(c) 2017 Intel Corporation
>>  
>>  name = 'ethdev'
>> -version = 8
>> +version = 9
> 
> My copy of latest head in git shows this as still being 8. However, I see
> it's down as 9 in next-net. Therefore I think we need to put this patch
> into next-net, perhaps merging with the appropriate patch there which
> updates the Makefile.
> 
> Ferruh, perhaps you could look at this one?

Applied to dpdk-next-net/master, thanks.

(Not able to squash because next-net pulled from main tree and the original
commit is now part of main tree)

  reply	other threads:[~2018-04-05 17:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 11:26 [PATCH 00/13] build: fix library version in meson build Andrew Rybchenko
2018-03-20 11:26 ` [PATCH 01/13] net/bonding: " Andrew Rybchenko
2018-03-23 21:31   ` Bruce Richardson
2018-03-27 16:43   ` [dpdk-stable] " Thomas Monjalon
2018-03-27 20:26     ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 02/13] net/i40e: " Andrew Rybchenko
2018-03-23 21:32   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 03/13] net/ixgbe: " Andrew Rybchenko
2018-03-23 21:37   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 04/13] net/null: " Andrew Rybchenko
2018-03-23 21:37   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 05/13] net/ring: " Andrew Rybchenko
2018-03-23 21:38   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 06/13] bitratestats: " Andrew Rybchenko
2018-03-23 21:39   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 07/13] cryptodev: " Andrew Rybchenko
2018-03-23 21:40   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 08/13] eventdev: " Andrew Rybchenko
2018-03-23 21:40   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 09/13] mempool: " Andrew Rybchenko
2018-03-23 21:41   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 10/13] pdump: " Andrew Rybchenko
2018-03-23 21:42   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 11/13] table: " Andrew Rybchenko
2018-03-23 21:42   ` Bruce Richardson
2018-03-20 11:26 ` [PATCH 12/13] ethdev: " Andrew Rybchenko
2018-03-23 21:46   ` Bruce Richardson
2018-04-05 17:33     ` Ferruh Yigit [this message]
2018-03-20 11:26 ` [PATCH 13/13] meter: " Andrew Rybchenko
2018-03-23 21:48   ` Bruce Richardson
2018-03-23 21:50 ` [PATCH 00/13] build: " Bruce Richardson
2018-03-27 22:08   ` 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=f59ee483-bf07-7f46-beca-29f1c9df7241@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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.