dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 355] Meson build failure due to libibverbs-dev upgrade (version=45mlnx1-1.45101)
Date: Mon, 02 Dec 2019 17:14:24 +0000	[thread overview]
Message-ID: <bug-355-3-PfQko2VQay@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-355-3@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=355

Dharmik Thakkar (dharmik.thakkar@arm.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED

--- Comment #14 from Dharmik Thakkar (dharmik.thakkar@arm.com) ---
I will move the ibverbs issue to a new ticket.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2019-12-02 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 18:45 [dpdk-dev] [Bug 355] Meson build failure bugzilla
2019-10-23 10:15 ` Bruce Richardson
2019-12-02 17:14 ` 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-355-3-PfQko2VQay@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).