DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net,
	Reshma Pattan <reshma.pattan@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH 1/2] build: cleanup libpcap dependent components
Date: Mon, 8 Nov 2021 08:57:27 -0800	[thread overview]
Message-ID: <20211108085727.6c2950b6@hermes.local> (raw)
In-Reply-To: <20211108100920.31083-1-david.marchand@redhat.com>

On Mon,  8 Nov 2021 11:09:18 +0100
David Marchand <david.marchand@redhat.com> wrote:

> The RTE_PORT_PCAP variable is used to signal libpcap availability,
> though its name seems to refer to pcap support in the port library.
> Prefer a generic name and add explicit link dependencies where needed.
> 
> Fixes: 7a944656b33f ("test/pcapng: test pcapng library")
> Fixes: 2eccf6afbea9 ("bpf: add function to convert classic BPF to DPDK BPF")
> Fixes: cbb44143be74 ("app/dumpcap: add new packet capture application")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Thanks for fixing.

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  parent reply	other threads:[~2021-11-08 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 10:09 David Marchand
2021-11-08 10:09 ` [dpdk-dev] [PATCH 2/2] test: fix dependency on pcapng David Marchand
2021-11-08 16:57 ` Stephen Hemminger [this message]
2021-11-10 10:57   ` [dpdk-dev] [PATCH 1/2] build: cleanup libpcap dependent components 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=20211108085727.6c2950b6@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=mdr@ashroe.eu \
    --cc=reshma.pattan@intel.com \
    --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).