From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <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: Wed, 10 Nov 2021 11:57:57 +0100 [thread overview]
Message-ID: <CAJFAV8yrrCRsT5CPgWTSp+g_qyGxw6o5+nrBavNxtf4NdOHddg@mail.gmail.com> (raw)
In-Reply-To: <20211108085727.6c2950b6@hermes.local>
On Mon, Nov 8, 2021 at 5:57 PM Stephen Hemminger
<stephen@networkplumber.org> 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>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-11-10 10:58 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 ` [dpdk-dev] [PATCH 1/2] build: cleanup libpcap dependent components Stephen Hemminger
2021-11-10 10:57 ` David Marchand [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=CAJFAV8yrrCRsT5CPgWTSp+g_qyGxw6o5+nrBavNxtf4NdOHddg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.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=stephen@networkplumber.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 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).