DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 848] gcc12 build error, app/test
Date: Fri, 24 Jun 2022 08:27:14 +0000	[thread overview]
Message-ID: <bug-848-3-xBs1Loe8qp@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-848-3@http.bugs.dpdk.org/>

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

David Marchand (david.marchand@redhat.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |david.marchand@redhat.com
         Resolution|---                         |FIXED

--- Comment #1 from David Marchand (david.marchand@redhat.com) ---
Fixed in commit 6e108b6a7c0c ("test/ipsec: fix build with GCC 12").

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

      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:01 [dpdk-dev] " 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-848-3-xBs1Loe8qp@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).