From: Thomas Monjalon <thomas@monjalon.net>
To: Amr Mokhtar <amr.mokhtar@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] bb/null: fix exported dynamic log type
Date: Tue, 06 Feb 2018 01:41:28 +0100 [thread overview]
Message-ID: <1832769.nzpftQVA6k@xps> (raw)
In-Reply-To: <1517869651-145451-1-git-send-email-amr.mokhtar@intel.com>
05/02/2018 23:27, Amr Mokhtar:
> This patch fixes shared library compilation due to undefined
> reference to an exported variable 'bbdev_logtype'.
> In this fix, the logtype is converted to static in the bbdev lib
> and in the bbdev null pmd.
>
> Fixes: 7dc2b1589440 ("bb/null: add null base band device driver")
> Cc: thomas@monjalon.net
>
> Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
It probably requires a rebase because it does not apply cleanly
on the master branch.
next prev parent reply other threads:[~2018-02-06 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 22:27 Amr Mokhtar
2018-02-06 0:41 ` Thomas Monjalon [this message]
2018-02-06 13:29 ` [dpdk-dev] [PATCH v2] bbdev: " Amr Mokhtar
2018-02-06 17:50 ` 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=1832769.nzpftQVA6k@xps \
--to=thomas@monjalon.net \
--cc=amr.mokhtar@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 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).