From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 921] meson build warnings with 0.61.1
Date: Wed, 02 Feb 2022 14:45:48 +0000 [thread overview]
Message-ID: <bug-921-3-vvFTrppUl9@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-921-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=921
Thomas Monjalon (thomas@monjalon.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Thomas Monjalon (thomas@monjalon.net) ---
Resolved in http://git.dpdk.org/dpdk/commit/?id=ecb904cc45
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-02-02 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 12:52 [Bug 921] meson build warnings with 0.61.1 bugzilla
2022-02-02 14:45 ` 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-921-3-vvFTrppUl9@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 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.