From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Simona Vetter <simona@ffwll.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
Tvrtko Ursulin <tursulin@ursulin.net>,
patches@lists.linux.dev
Subject: Re: [PATCH 0/5] Replace the dmabuf custom test framework with kunit
Date: Tue, 7 Apr 2026 09:35:30 -0300 [thread overview]
Message-ID: <20260407123530.GA3395114@nvidia.com> (raw)
In-Reply-To: <c088698d-0bb2-4b0a-acad-946ec3df5777@amd.com>
On Mon, Mar 02, 2026 at 02:58:55PM +0100, Christian König wrote:
> >> No idea when or even if I have time to review that, but feel free to
> >> add my Acked-by should that go upstream.
> >
> > I'm confused by this statement, aren't you the person who would send
> > it upstream?
>
> Sumit and me are the maintainers for DMA-buf, but the
> drm-misc-next/-fixes branches used to send DMA-buf patches upstream
> are used by much more people.
>
> > It is just a kunit, I wouldn't expect an intensive review. The tests
> > still run after all
>
> When somebody else has time to take a look over those patches I
> think we can push them to drm-misc-next ASAP. I just wanted to note
> that I'm ok with that as maintainer and those patches doesn't need
> to be reviewed by me.
So, am I supposed to do something with this? It's been a month, I
didn't think this series would be an issue.
Thanks,
Jason
next prev parent reply other threads:[~2026-04-07 12:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 18:57 [PATCH 0/5] Replace the dmabuf custom test framework with kunit Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 1/5] dma-buf: Change st-dma-resv.c to use kunit Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 2/5] dma-buf: Change st-dma-fence.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 3/5] dma-buf: Change st-dma-fence-unwrap.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 4/5] dma-buf: Change st-dma-fence-chain.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 5/5] dma-buf: Remove the old selftest Jason Gunthorpe
2026-03-01 19:52 ` ✗ i915.CI.BAT: failure for Replace the dmabuf custom test framework with kunit Patchwork
2026-03-01 20:03 ` Jason Gunthorpe
2026-03-02 11:43 ` [PATCH 0/5] " Christian König
2026-03-02 13:01 ` Jason Gunthorpe
2026-03-02 13:58 ` Christian König
2026-04-07 12:35 ` Jason Gunthorpe [this message]
2026-04-16 10:37 ` Christian König
2026-04-16 12:00 ` Jason Gunthorpe
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=20260407123530.GA3395114@nvidia.com \
--to=jgg@nvidia.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=tursulin@ursulin.net \
/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.