DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 923] i40e PMD contains copy-pasted bug from mempool library
Date: Thu, 14 Jul 2022 15:46:42 +0000	[thread overview]
Message-ID: <bug-923-3-P8RewPF0aO@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-923-3@http.bugs.dpdk.org/>

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

Morten Brørup (mb@smartsharesystems.com) changed:

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

--- Comment #1 from Morten Brørup (mb@smartsharesystems.com) ---
Copy-pasting internal code and not using the mempool API causes more problems
than just the risk of spreading bugs from the library it is copied from to the
destinations where it is copied.

*** This bug has been marked as a duplicate of bug 1052 ***

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

      parent reply	other threads:[~2022-07-14 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  8:43 bugzilla
2022-01-20  9:06 ` Morten Brørup
2022-07-14 15: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-923-3-P8RewPF0aO@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).