DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dylan Schneider <schneide@qti.qualcomm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Zhirun Yan <yanzhirun_163@163.com>
Subject: Re: [PATCH v2] pcapng: allow any protocol link type for the interface block
Date: Mon, 9 Jun 2025 09:24:55 -0700	[thread overview]
Message-ID: <20250609092455.241e4273@hermes.local> (raw)
In-Reply-To: <DM8PR02MB8171CB561807D476C05E013DE96BA@DM8PR02MB8171.namprd02.prod.outlook.com>

On Mon, 9 Jun 2025 15:51:03 +0000
Dylan Schneider <schneide@qti.qualcomm.com> wrote:

> In this case, is it best to just pass 1 with a comment saying that is DLT_EN10MB? Or is there a way we can get it defined in all configs?

Just add a dependency on libpcap like other places do (see pcap PMD)

  reply	other threads:[~2025-06-09 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 17:16 [PATCH] " Schneide
2025-05-29 19:31 ` Stephen Hemminger
2025-05-29 19:57 ` Stephen Hemminger
2025-06-05 23:02 ` [PATCH v2] " Schneide
2025-06-06 15:13   ` Stephen Hemminger
2025-06-06 21:52 ` Schneide
2025-06-08 22:16   ` Stephen Hemminger
2025-06-08 22:19   ` Stephen Hemminger
2025-06-08 22:23   ` Stephen Hemminger
2025-06-08 22:30   ` Stephen Hemminger
2025-06-08 22:34   ` Stephen Hemminger
2025-06-09 15:51     ` Dylan Schneider
2025-06-09 16:24       ` Stephen Hemminger [this message]
2025-06-09 21:19 ` Schneide

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=20250609092455.241e4273@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=reshma.pattan@intel.com \
    --cc=schneide@qti.qualcomm.com \
    --cc=thomas@monjalon.net \
    --cc=yanzhirun_163@163.com \
    /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).