All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, Ray Kinsella <mdr@ashroe.eu>,
	Thomas Monjalon <thomas@monjalon.net>,
	Neil Horman <nhorman@tuxdriver.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Alfredo Cardigliano <cardigliano@ntop.org>,
	Mahipal Challa <mchalla@marvell.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [dpdk-dev] [PATCH v6 1/1] abi: change references to abi 20.0.1 to abi v21
Date: Thu, 30 Apr 2020 11:27:25 +0100	[thread overview]
Message-ID: <20200430102726.295773-1-mdr@ashroe.eu> (raw)
In-Reply-To: <20200420093421.68984-1-mdr@ashroe.eu>

Sending again, as I missed the cover letter last time.

v6:
 * combined policy and versioning in the maintainers file.

Ray Kinsella (1):
  abi: change references to abi 20.0.1 to abi v21

 MAINTAINERS                                            | 10 +++++-----
 devtools/libabigail.abignore                           |  5 +++++
 drivers/common/iavf/rte_common_iavf_version.map        |  2 +-
 drivers/common/mlx5/rte_common_mlx5_version.map        |  2 +-
 .../common/octeontx2/rte_common_octeontx2_version.map  |  2 +-
 drivers/net/ionic/rte_pmd_ionic_version.map            |  2 +-
 .../octeontx2_ep/rte_rawdev_octeontx2_ep_version.map   |  2 +-
 drivers/vdpa/mlx5/rte_pmd_mlx5_vdpa_version.map        |  2 +-
 lib/librte_meter/rte_meter_version.map                 |  2 +-
 9 files changed, 17 insertions(+), 12 deletions(-)

--
2.23.0

  parent reply	other threads:[~2020-04-30 11:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  9:34 [dpdk-dev] [PATCH] abi: change references to abi 20.0.1 to abi v21 Ray Kinsella
2020-04-20 11:57 ` Ray Kinsella
2020-04-20 12:20   ` David Marchand
2020-04-20 15:25     ` Ray Kinsella
2020-04-22  8:07     ` Ray Kinsella
2020-04-22  8:11       ` David Marchand
2020-04-22  8:18       ` Thomas Monjalon
2020-04-22  8:28         ` Ray Kinsella
2020-04-23  6:41 ` [dpdk-dev] [PATCH v2] " Ray Kinsella
2020-04-24  9:15   ` Thomas Monjalon
2020-04-24 14:10   ` David Marchand
2020-04-24 14:50     ` Ray Kinsella
2020-04-24 15:01       ` David Marchand
2020-04-29 12:19       ` Dodji Seketeli
2020-04-30  8:23         ` Ray Kinsella
2020-04-27  9:06 ` [dpdk-dev] [PATCH v3] " Ray Kinsella
2020-04-27  9:06   ` Ray Kinsella
2020-04-27 13:45 ` [dpdk-dev] [PATCH v4] " Ray Kinsella
2020-04-27 13:45   ` Ray Kinsella
2020-04-30 10:21 ` [dpdk-dev] [PATCH v5] " Ray Kinsella
2020-04-30 10:27 ` Ray Kinsella [this message]
2020-04-30 10:27   ` [dpdk-dev] [PATCH v6 1/1] " Ray Kinsella
2020-05-04 22:23     ` Thomas Monjalon
2020-05-04 22:05   ` 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=20200430102726.295773-1-mdr@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=beilei.xing@intel.com \
    --cc=cardigliano@ntop.org \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=jingjing.wu@intel.com \
    --cc=matan@mellanox.com \
    --cc=mchalla@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=nhorman@tuxdriver.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@mellanox.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.