All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1413] Build initial list of device capabilities required by testsuites we are trying to write this year
Date: Wed, 10 Apr 2024 16:30:13 +0000	[thread overview]
Message-ID: <bug-1413-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1413
           Summary: Build initial list of device capabilities required by
                    testsuites we are trying to write this year
           Product: DPDK
           Version: 24.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: DTS
          Assignee: dev@dpdk.org
          Reporter: probb@iol.unh.edu
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

https://patchwork.dpdk.org/project/dpdk/patch/20240301155416.96960-1-juraj.linkes@pantheon.tech/

Juraj has this RFC for skipping testcases based on capabilities, but it only
checks for scattered_rx. He has requested a more comprehensive list of what
capabilities we may need to check for going forward. 

I think this is a good first ticket for Prince at UNH to work on.

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

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

             reply	other threads:[~2024-04-10 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 16:30 bugzilla [this message]
     [not found] <bug-1413-3@https.bugs.dpdk.org/>
2025-07-17 13:52 ` [DPDK/DTS Bug 1413] Build initial list of device capabilities required by testsuites we are trying to write this year bugzilla

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-1413-3@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.