DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH dpdk 0/2] Fix dynamic link of driver symbols with pkgconf
Date: Thu, 15 Oct 2026 13:27:06 +0200	[thread overview]
Message-ID: <DM5DJCJL2UMS.C2JGDOMKQ6W1@redhat.com> (raw)
In-Reply-To: <atCt9qNiM4l2x6hT@bricha3-mobl1.ger.corp.intel.com>

Bruce Richardson, Oct 15, 2026 at 12:41:
> While the changes in the two patches are ok, I don't see how they affect
> pkg-config. The first patch just renames a variable for clarity, and the
> second only affects applications linking using a meson subproject rather
> than a .pc file.

Indeed, I had forgotten about updating the correct variable. v2 should
be good.


-- 
Robin

# To order, call toll-free.


  reply	other threads:[~2026-10-15 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 10:09 [PATCH dpdk 0/2] Fix dynamic link of driver symbols with pkgconf Robin Jarry
2026-10-15 10:09 ` [PATCH dpdk 1/2] meson: rename static drivers list Robin Jarry
2026-10-15 10:36   ` Bruce Richardson
2026-10-15 10:09 ` [PATCH dpdk 2/2] meson: add drivers to dynamic libraries Robin Jarry
2026-10-15 10:40   ` Bruce Richardson
2026-10-15 10:41 ` [PATCH dpdk 0/2] Fix dynamic link of driver symbols with pkgconf Bruce Richardson
2026-10-15 11:27   ` Robin Jarry [this message]
2026-10-15 11:26 ` [PATCH dpdk v2 " Robin Jarry
2026-10-15 11:26   ` [PATCH dpdk v2 1/2] meson: rename static drivers list Robin Jarry
2026-10-15 11:26   ` [PATCH dpdk v2 2/2] meson: add drivers to dynamic libraries Robin Jarry
2026-10-15 11:52     ` Bruce Richardson
2026-10-15 12:06       ` Robin Jarry
2026-10-15 12:18         ` Bruce Richardson
2026-10-15 14:47           ` Robin Jarry

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=DM5DJCJL2UMS.C2JGDOMKQ6W1@redhat.com \
    --to=rjarry@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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