From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 861] gcc12 build error, common/cpt
Date: Fri, 24 Jun 2022 08:27:54 +0000 [thread overview]
Message-ID: <bug-861-3-e1jDYrzpbv@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-861-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=861
David Marchand (david.marchand@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |david.marchand@redhat.com
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from David Marchand (david.marchand@redhat.com) ---
Fixed in commit 3aa16821ab3e ("common/cpt: fix build with GCC 12").
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-06-24 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:49 [dpdk-dev] [Bug 861] gcc12 build error, app/test bugzilla
2022-06-24 8:27 ` 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-861-3-e1jDYrzpbv@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.