From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Deepak R Varma <drv@mailo.com>, David Airlie <airlied@gmail.com>,
intel-gfx@lists.freedesktop.org,
Saurabh Singh Sengar <ssengar@microsoft.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Praveen Kumar <kumarpraveen@linux.microsoft.com>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
Date: Fri, 20 Jan 2023 10:20:17 +0800 [thread overview]
Message-ID: <Y8n6YWMjRpT812B+@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <Y8m+xBhGCa3kgcO2@intel.com>
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
On 2023.01.19 17:05:56 -0500, Rodrigo Vivi wrote:
>
> It still doesn't apply in drm-intel-next.
> Could you please take it through your branch?
>
sure, I'll pick it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2023-01-20 2:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 18:29 [PATCH 0/2] drm/i915/gvt: Avoid full proxy f_ops " Deepak R Varma
2023-01-10 18:29 ` [PATCH 1/2] drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb " Deepak R Varma
2023-01-10 18:30 ` [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status " Deepak R Varma
2023-01-10 18:49 ` Rodrigo Vivi
2023-01-11 10:02 ` Rodrigo Vivi
2023-01-11 14:53 ` Deepak R Varma
2023-01-11 15:00 ` Rodrigo Vivi
2023-01-11 15:16 ` Deepak R Varma
2023-01-11 15:24 ` Rodrigo Vivi
2023-01-16 5:44 ` Zhenyu Wang
2023-01-17 19:29 ` [Intel-gfx] " Rodrigo Vivi
2023-01-18 4:48 ` Deepak R Varma
2023-01-18 16:44 ` Rodrigo Vivi
2023-01-19 1:26 ` Zhenyu Wang
2023-01-19 22:05 ` Rodrigo Vivi
2023-01-20 2:20 ` Zhenyu Wang [this message]
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=Y8n6YWMjRpT812B+@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=drv@mailo.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kumarpraveen@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=ssengar@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome