From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Linux DRI Development" <dri-devel@lists.freedesktop.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Rob Clark" <robin.clark@oss.qualcomm.com>,
"Antonino Maniscalco" <antomani103@gmail.com>,
"André Almeida" <andrealmeid@igalia.com>,
"Raag Jadav" <raag.jadav@intel.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH] drm/gpuvm: Wrap drm_gpuvm_sm_map_exec_lock() expected usage in literal code block
Date: Wed, 9 Jul 2025 15:40:36 +0700 [thread overview]
Message-ID: <aG4rBBJE_KEhkAfu@archie.me> (raw)
In-Reply-To: <aade485e-0880-4c68-9b37-d8a27dc122e3@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
On Wed, Jul 09, 2025 at 09:37:36AM +0200, Danilo Krummrich wrote:
> I assume this has to go through the MSM tree?
Of course!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-07-09 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 2:45 [PATCH] drm/gpuvm: Wrap drm_gpuvm_sm_map_exec_lock() expected usage in literal code block Bagas Sanjaya
2025-07-09 5:26 ` Randy Dunlap
2025-07-09 7:37 ` Danilo Krummrich
2025-07-09 8:40 ` Bagas Sanjaya [this message]
2025-08-17 23:24 ` Randy Dunlap
2025-08-17 23:45 ` Stephen Rothwell
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=aG4rBBJE_KEhkAfu@archie.me \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=antomani103@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=raag.jadav@intel.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=sfr@canb.auug.org.au \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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