From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 282] Fix missing headers in FreeBSD CURRENT build
Date: Tue, 21 May 2019 01:54:36 +0000 [thread overview]
Message-ID: <bug-282-3@http.bugs.dpdk.org/> (raw)
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:
--- kernel/freebsd/contigmem/contigmem.c.orig 2018-09-05 14:29:02 UTC
+++ kernel/freebsd/contigmem/contigmem.c
@@ -9,9 +9,12 @@
#include <sys/bio.h>
#include <sys/bus.h>
#include <sys/conf.h>
+#include <sys/eventhandler.h>
#include <sys/kernel.h>
+#include <sys/lock.h>
#include <sys/malloc.h>
#include <sys/module.h>
+#include <sys/mutex.h>
#include <sys/proc.h>
#include <sys/rwlock.h>
#include <sys/systm.h>
--- kernel/freebsd/nic_uio/nic_uio.c.orig 2018-09-05 14:29:02 UTC
+++ kernel/freebsd/nic_uio/nic_uio.c
@@ -9,6 +9,7 @@
#include <sys/kernel.h> /* types used in module initialization */
#include <sys/conf.h> /* cdevsw struct */
#include <sys/bus.h> /* structs, prototypes for pci bus stuff and DEVMETHOD */
+#include <sys/lock.h> /* used by vm_pager.h => MPASS() */
#include <sys/rman.h>
#include <sys/systm.h>
#include <sys/rwlock.h>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-05-21 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:54 bugzilla [this message]
2019-05-21 3:04 ` Stephen Hemminger
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=bug-282-3@http.bugs.dpdk.org/ \
--to=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 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).