public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Cliff Burdick <cburdick@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Subject: Re: [PATCH v4 0/2] support dmabuf
Date: Thu, 5 Feb 2026 14:50:13 -0800	[thread overview]
Message-ID: <20260205145013.78125c63@phoenix.local> (raw)
In-Reply-To: <SN7PR12MB6960C2AF8C689108DCDFF356AB99A@SN7PR12MB6960.namprd12.prod.outlook.com>

On Thu, 5 Feb 2026 20:25:01 +0000
Cliff Burdick <cburdick@nvidia.com> wrote:

> > Any new library like this needs standalone tests so that it gets covered in CI etc.  
> 
> I did not see any existing GPU tests, and this would require a GPU to test along with a 5.15+ Linux kernel. Do those systems exist in the test infrastructure?

That was a mistake in allowing them in.
The problem was GPU requires CUDA, but that could have been handled.

  reply	other threads:[~2026-02-05 22:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 17:44 [PATCH 0/2] support dmabuf Cliff Burdick
2026-01-27 17:44 ` [PATCH 1/2] eal: " Cliff Burdick
2026-01-29  1:48   ` Stephen Hemminger
2026-01-29  1:51   ` Stephen Hemminger
2026-01-27 17:44 ` [PATCH 2/2] common/mlx5: " Cliff Burdick
2026-01-27 19:21   ` [REVIEW] " Stephen Hemminger
2026-01-28 14:30     ` David Marchand
2026-01-28 17:10       ` Stephen Hemminger
2026-01-28 17:43       ` Stephen Hemminger
2026-02-03 17:34     ` Cliff Burdick
2026-01-29  1:51   ` [PATCH 2/2] " Stephen Hemminger
2026-01-28  0:04 ` [PATCH 0/2] " Stephen Hemminger
2026-02-03 17:18   ` Cliff Burdick
2026-02-03 22:26 ` [PATCH v2 " Cliff Burdick
2026-02-03 22:26   ` [PATCH v2 1/2] eal: " Cliff Burdick
2026-02-03 22:26   ` [PATCH v2 2/2] common/mlx5: " Cliff Burdick
2026-02-03 23:02   ` [PATCH v3 0/2] " Cliff Burdick
2026-02-03 23:02     ` [PATCH v3 1/2] eal: " Cliff Burdick
2026-02-03 23:02     ` [PATCH v3 2/2] common/mlx5: " Cliff Burdick
2026-02-04 15:50     ` [PATCH v4 0/2] " Cliff Burdick
2026-02-04 15:50       ` [PATCH v4 1/2] eal: " Cliff Burdick
2026-02-12 13:57         ` Burakov, Anatoly
2026-02-04 15:50       ` [PATCH v4 2/2] common/mlx5: " Cliff Burdick
2026-02-05 18:48       ` [PATCH v4 0/2] " Stephen Hemminger
2026-02-05 20:25         ` Cliff Burdick
2026-02-05 22:50           ` Stephen Hemminger [this message]
2026-03-31  3:15       ` Stephen Hemminger

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=20260205145013.78125c63@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=cburdick@nvidia.com \
    --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