From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 282] Fix missing headers in FreeBSD CURRENT build
Date: Mon, 20 May 2019 20:04:29 -0700 [thread overview]
Message-ID: <20190520200429.4ef3cea7@hermes.lan> (raw)
In-Reply-To: <bug-282-3@http.bugs.dpdk.org/>
On Tue, 21 May 2019 01:54:36 +0000
bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=282
>
> Bug ID: 282
> Summary: Fix missing headers in FreeBSD CURRENT build
> Product: DPDK
> Version: 18.05
> Hardware: All
> OS: FreeBSD
> Status: CONFIRMED
> Severity: normal
> Priority: Normal
> Component: core
> Assignee: dev@dpdk.org
> Reporter: cem@FreeBSD.org
> Target Milestone: ---
>
> After header pollution cleanup, some files in DPDK 18.05.1 no longer compile.
> The fixes are straightforward. I don't know if the problem is still present in
> newer DPDK but I wouldn't be surprised if it were. Feel free to consider these
> patches in the public domain, or CC0 if you're European:
>
All patches must be licensed by the same license as the original code.
That is BSD-3 in this case.
Please don't send with other licenses.
next prev parent reply other threads:[~2019-05-21 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:54 [dpdk-dev] [Bug 282] Fix missing headers in FreeBSD CURRENT build bugzilla
2019-05-21 3:04 ` Stephen Hemminger [this message]
2019-07-12 16:07 ` bugzilla
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=20190520200429.4ef3cea7@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bugzilla@dpdk.org \
--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 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.