From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 282] Fix missing headers in FreeBSD CURRENT build
Date: Fri, 12 Jul 2019 16:07:48 +0000 [thread overview]
Message-ID: <bug-282-3-4WIEWLSLi7@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-282-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=282
Conrad Meyer (cem@FreeBSD.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #6 from Conrad Meyer (cem@FreeBSD.org) ---
(In reply to Herakliusz from comment #5)
> This issue had been fixed
> on 19.08. As I said before 18.05 is no longer supported so there will be no
> back-port to 18.05 but more than likely this will get back-ported to 18.11
> LTS as well.
Right, 1c7191e7349e612a44523cde7fa2340ffe8f1c8f works for me. I just want it
fixed in the development branch; I don't care about 18.05 or any LTS release in
particular. Thanks Bruce Richardson!
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-07-12 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:54 bugzilla
2019-05-21 3:04 ` Stephen Hemminger
2019-07-12 16:07 ` bugzilla [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=bug-282-3-4WIEWLSLi7@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).