All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	ferruh.yigit@intel.com
Subject: Re: [PATCH 00/13] build: fix library version in meson build
Date: Wed, 28 Mar 2018 00:08:25 +0200	[thread overview]
Message-ID: <3620346.XgfVjcHgiy@xps> (raw)
In-Reply-To: <20180323215048.GN19100@bricha3-MOBL.ger.corp.intel.com>

23/03/2018 22:50, Bruce Richardson:
> On Tue, Mar 20, 2018 at 11:26:14AM +0000, Andrew Rybchenko wrote:
> > Library version is specified in two places: Makefile and meson.build.
> > It is out-of-sync in a number of cases.
> > 
> > Andrew Rybchenko (13):
> >   net/bonding: fix library version in meson build
> >   net/i40e: fix library version in meson build
> >   net/ixgbe: fix library version in meson build
> >   net/null: fix library version in meson build
> >   net/ring: fix library version in meson build
> >   bitratestats: fix library version in meson build
> >   cryptodev: fix library version in meson build
> >   eventdev: fix library version in meson build
> >   mempool: fix library version in meson build
> >   pdump: fix library version in meson build
> >   table: fix library version in meson build
> >   ethdev: fix library version in meson build
> >   meter: fix library version in meson build
> > 
> 
> Hi Thomas,
> 
> these are all trivial fixes, so I think they should go into the main tree
> directly rather than going via next-build. Can you apply them, please -
> apart from patch 12, which should go to Ferruh's tree, I think?

Applied, except patch 12 (ethdev), thanks

      reply	other threads:[~2018-03-27 22:08 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
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 [this message]

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=3620346.XgfVjcHgiy@xps \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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 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.