patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: Jerin Jacob <jerinj@marvell.com>,
	john.mcnamara@intel.com, ray.kinsella@intel.com,
	bruce.richardson@intel.com, thomas@monjalon.net,
	david.marchand@redhat.com, pbhagavatula@caviumnetworks.com,
	stable@dpdk.org
Subject: [dpdk-stable] [PATCH v6 08/10] drivers/octeontx: add missing public symbol
Date: Wed,  6 Nov 2019 16:54:27 +0000	[thread overview]
Message-ID: <8499dd3e0430013a59eaef62aa9f42adeb66e952.1573059201.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1573059201.git.anatoly.burakov@intel.com>
In-Reply-To: <cover.1573059201.git.anatoly.burakov@intel.com>

The logtype symbol was missing from the .map file. Add it.

Fixes: d8dd31652cf4 ("common/octeontx: move mbox to common folder")
Cc: pbhagavatula@caviumnetworks.com
Cc: stable@dpdk.org

Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
---

Notes:
    v2:
    - add this patch to avoid compile breakage when bumping ABI

 drivers/common/octeontx/rte_common_octeontx_version.map | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/common/octeontx/rte_common_octeontx_version.map b/drivers/common/octeontx/rte_common_octeontx_version.map
index f04b3b7f8a..a9b3cff9bc 100644
--- a/drivers/common/octeontx/rte_common_octeontx_version.map
+++ b/drivers/common/octeontx/rte_common_octeontx_version.map
@@ -1,6 +1,7 @@
 DPDK_18.05 {
 	global:
 
+	octeontx_logtype_mbox;
 	octeontx_mbox_set_ram_mbox_base;
 	octeontx_mbox_set_reg;
 	octeontx_mbox_send;
-- 
2.17.1

  parent reply	other threads:[~2019-11-06 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1574270323.git.anatoly.burakov@intel.com>
     [not found] ` <cover.1573230233.git.anatoly.burakov@intel.com>
     [not found]   ` <cover.1573059201.git.anatoly.burakov@intel.com>
     [not found]     ` <cover.1571910363.git.anatoly.burakov@intel.com>
     [not found]       ` <cover.1571322634.git.anatoly.burakov@intel.com>
     [not found]         ` <cover.1571245316.git.anatoly.burakov@intel.com>
     [not found]           ` <cover.1571229052.git.anatoly.burakov@intel.com>
     [not found]             ` <20190930092139.2440-1-marcinx.baran@intel.com>
2019-10-16 12:43               ` [dpdk-stable] [PATCH v2 " Anatoly Burakov
2019-10-16 17:03             ` [dpdk-stable] [PATCH v3 7/9] " Anatoly Burakov
2019-10-17 14:31           ` [dpdk-stable] [PATCH v4 08/10] " Anatoly Burakov
2019-10-24  9:46         ` [dpdk-stable] [PATCH v5 " Anatoly Burakov
2019-11-06 16:54       ` Anatoly Burakov [this message]
2019-11-08 16:25     ` [dpdk-stable] [PATCH v7 " Anatoly Burakov
2019-11-20 17:23   ` [dpdk-stable] [PATCH v8 10/12] " Anatoly Burakov

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=8499dd3e0430013a59eaef62aa9f42adeb66e952.1573059201.git.anatoly.burakov@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=ray.kinsella@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).