All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36
Date: Wed, 15 Jun 2022 08:46:29 +0000	[thread overview]
Message-ID: <bug-1008-3-e99oQ63ITT@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1008-3@http.bugs.dpdk.org/>

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

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

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

--- Comment #1 from David Marchand (david.marchand@redhat.com) ---
Thanks, there were several other reports for the various issues, I prefer to
close this one. Feel free to open a bugzilla for any remaining issue that has
no assigned bz.

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

      reply	other threads:[~2022-06-15  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  8:40 [Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36 bugzilla
2022-06-15  8:46 ` 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-1008-3-e99oQ63ITT@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.