From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] examples: fix linking against specific drivers
Date: Mon, 2 Nov 2020 17:47:45 +0000 [thread overview]
Message-ID: <ea6592cce52d4569824c0faf3ec197af@intel.com> (raw)
In-Reply-To: <CAJFAV8x1CqO-qKQV0s-wiKctzurOp95aWj0w8bqE-WQ+Dc4_Qw@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, October 30, 2020 1:36 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: dev <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] [PATCH] examples: fix linking against specific
> drivers
>
> On Tue, Oct 27, 2020 at 6:20 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > Some example apps rely on driver-specific functionality and link
> explicitly
> > against those drivers. These apps need their makefiles updated to take
> > account of the renaming of the driver libs.
> >
> > Fixes: a20b2c01a7a1 ("build: standardize component names and defines")
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
>
> Applied, thanks Bruce.
>
>
> I think the documentation would also need some fixes as I can see a
> lot of references to librte_pmd_.
>
First draft patchset sent, based off grepping the docs for "librte_pmd_".
http://patches.dpdk.org/project/dpdk/list/?series=13578
/Bruce
prev parent reply other threads:[~2020-11-02 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 17:19 [dpdk-dev] [PATCH] examples: fix linking against specific drivers Bruce Richardson
2020-10-30 13:35 ` David Marchand
2020-11-02 17:47 ` Richardson, Bruce [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=ea6592cce52d4569824c0faf3ec197af@intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@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 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.