From: Danilo Krummrich <dakr@redhat.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: matt.coster@imgtec.com, sarah.walker@imgtec.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
donald.robson@imgtec.com
Subject: Re: [PATCH drm-misc-next v2 0/2] PowerVR VM fixes
Date: Tue, 5 Dec 2023 16:40:40 +0100 [thread overview]
Message-ID: <ZW9EeFWWZ0BMWIPq@pollux> (raw)
In-Reply-To: <j6w6ccewlvoosop77ug56r3sqoi4hglj3ejkyfw4dj3s3pdsw5@b473njzq5u3d>
On Tue, Dec 05, 2023 at 04:35:00PM +0100, Maxime Ripard wrote:
> Hi,
>
> On Wed, Nov 29, 2023 at 11:07:59PM +0100, Danilo Krummrich wrote:
> > Some major GPUVM changes landed just before v8 of the PowerVR series. Since v8
> > went in rather quickly (review process was finished otherwise) I haven't had the
> > chance to review the subsequent code changes.
> >
> > Hence, this series with a few fixes in this context. Plus a minor GPUVM patch to
> > make the drm_gpuvm_prepare_* helpers useful for PowerVR.
>
> This doesn't apply on drm-misc-next anymore, could you rebase and
> resend?
I already applied the two patches to drm-misc-next.
- Danilo
>
> Thanks!
> Maxime
WARNING: multiple messages have this Message-ID (diff)
From: Danilo Krummrich <dakr@redhat.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: sarah.walker@imgtec.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, matt.coster@imgtec.com,
donald.robson@imgtec.com
Subject: Re: [PATCH drm-misc-next v2 0/2] PowerVR VM fixes
Date: Tue, 5 Dec 2023 16:40:40 +0100 [thread overview]
Message-ID: <ZW9EeFWWZ0BMWIPq@pollux> (raw)
In-Reply-To: <j6w6ccewlvoosop77ug56r3sqoi4hglj3ejkyfw4dj3s3pdsw5@b473njzq5u3d>
On Tue, Dec 05, 2023 at 04:35:00PM +0100, Maxime Ripard wrote:
> Hi,
>
> On Wed, Nov 29, 2023 at 11:07:59PM +0100, Danilo Krummrich wrote:
> > Some major GPUVM changes landed just before v8 of the PowerVR series. Since v8
> > went in rather quickly (review process was finished otherwise) I haven't had the
> > chance to review the subsequent code changes.
> >
> > Hence, this series with a few fixes in this context. Plus a minor GPUVM patch to
> > make the drm_gpuvm_prepare_* helpers useful for PowerVR.
>
> This doesn't apply on drm-misc-next anymore, could you rebase and
> resend?
I already applied the two patches to drm-misc-next.
- Danilo
>
> Thanks!
> Maxime
next prev parent reply other threads:[~2023-12-05 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:07 [PATCH drm-misc-next v2 0/2] PowerVR VM fixes Danilo Krummrich
2023-11-29 22:07 ` Danilo Krummrich
2023-11-29 22:08 ` [PATCH drm-misc-next v2 1/2] drm/gpuvm: fall back to drm_exec_lock_obj() Danilo Krummrich
2023-11-29 22:08 ` Danilo Krummrich
2023-11-29 22:08 ` [PATCH drm-misc-next v2 2/2] drm/imagination: vm: make use of GPUVM's drm_exec helper Danilo Krummrich
2023-11-29 22:08 ` Danilo Krummrich
2023-12-05 14:54 ` [EXTERNAL] [PATCH drm-misc-next v2 0/2] PowerVR VM fixes Donald Robson
2023-12-05 14:54 ` Donald Robson
2023-12-05 15:35 ` Maxime Ripard
2023-12-05 15:35 ` Maxime Ripard
2023-12-05 15:40 ` Danilo Krummrich [this message]
2023-12-05 15:40 ` Danilo Krummrich
2023-12-06 8:28 ` Maxime Ripard
2023-12-06 8:28 ` Maxime Ripard
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=ZW9EeFWWZ0BMWIPq@pollux \
--to=dakr@redhat.com \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=sarah.walker@imgtec.com \
/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.