All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1580] Nthw: array overrun
Date: Fri, 15 Nov 2024 16:42:29 +0000	[thread overview]
Message-ID: <bug-1580-3-28gqJOucqN@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1580-3@http.bugs.dpdk.org/>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

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

Stephen Hemminger (stephen@networkplumber.org) changed:

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

--- Comment #2 from Stephen Hemminger (stephen@networkplumber.org) ---
The scan was done by the owner of the PVS studio blog (not me) and appears to
have been rung against github main branch early in 24.11.

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

[-- Attachment #2: Type: text/html, Size: 2579 bytes --]

      reply	other threads:[~2024-11-15 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15  4:10 [DPDK/ethdev Bug 1580] Nthw: array overrun bugzilla
2024-11-15 16:42 ` 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-1580-3-28gqJOucqN@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.