From: David Marchand <david.marchand@redhat.com>
To: Abdelfattah Chehab <abdelfattah.chehab-ext@ekinops.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] vmbus: get current rte_vmbus_bus struct
Date: Wed, 13 Apr 2022 10:10:48 +0200 [thread overview]
Message-ID: <CAJFAV8ydwVRUqoryk=ZUPr2q7iYd9ZY9Dqfgz=miv7KK7H-Y0w@mail.gmail.com> (raw)
In-Reply-To: <PR1P264MB2030EB80D45C19826E935ADFDFEA9@PR1P264MB2030.FRAP264.PROD.OUTLOOK.COM>
On Wed, Apr 13, 2022 at 9:32 AM Abdelfattah Chehab
<abdelfattah.chehab-ext@ekinops.com> wrote:
>
> Hi All,
>
> FOREACH_DEVICE_ON_VMBUS needs rte_vmbus_bus to work on
>
> If static link to libdpdk.a : no issues
>
> If dynamic link to *.so: linker issue, global variable not found.
Not sure I really get your usecase, but this probably is a linking
issue on your side.
--
David Marchand
next prev parent reply other threads:[~2022-04-13 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 14:54 Abdelfattah Chehab
2022-04-13 8:10 ` David Marchand [this message]
2022-04-14 9:58 ` Abdelfattah Chehab
2022-07-09 7:54 ` David Marchand
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='CAJFAV8ydwVRUqoryk=ZUPr2q7iYd9ZY9Dqfgz=miv7KK7H-Y0w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=abdelfattah.chehab-ext@ekinops.com \
--cc=dev@dpdk.org \
--cc=stable@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 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).