From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw.linux@gmail.com>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
<zhi.wang.linux@gmail.com>, <jani.nikula@linux.intel.com>,
<joonas.lahtinen@linux.intel.com>, <tursulin@ursulin.net>,
<intel-gvt-dev@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>, <airlied@gmail.com>,
<simona@ffwll.ch>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] drm/i915/gvt: Deadcoding
Date: Thu, 9 Jan 2025 16:10:24 -0500 [thread overview]
Message-ID: <Z4A7QDtTrU6w2Yhv@intel.com> (raw)
In-Reply-To: <Z3uGjO36tfhQsnfp@dell-wzy>
On Mon, Jan 06, 2025 at 04:30:20PM +0900, Zhenyu Wang wrote:
> On Sun, Dec 22, 2024 at 12:25:09AM +0000, Dr. David Alan Gilbert wrote:
> > Note: zhenyuw@linux.intel.com's address bounces:
> >
>
> yeah, I've left Intel so can't use that box any more, looks Rodrigo hasn't
> queue up my address change patch yet. Rodrigo?
pushed to drm-intel-next now, although I was assuming this to come
on a gvt pull request...
what about this patch here? coming in a PR or should I take this
directly at drm-intel-next as well?
Thanks,
Rodrigo.
next prev parent reply other threads:[~2025-01-09 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 0:20 [PATCH 0/3] drm/i915/gvt: Deadcoding linux
2024-12-22 0:20 ` [PATCH 1/3] drm/i915/gvt: Remove intel_gvt_ggtt_h2g<->index linux
2024-12-22 0:20 ` [PATCH 2/3] drm/i915/gvt: Remove unused intel_vgpu_decode_sprite_plane linux
2024-12-22 0:20 ` [PATCH 3/3] drm/i915/gvt: Remove unused intel_gvt_in_force_nonpriv_whitelist linux
2024-12-22 0:25 ` [PATCH 0/3] drm/i915/gvt: Deadcoding Dr. David Alan Gilbert
2025-01-06 7:30 ` Zhenyu Wang
2025-01-09 21:10 ` Rodrigo Vivi [this message]
2025-01-10 10:49 ` GVT-g status (was: Re: [PATCH 0/3] drm/i915/gvt: Deadcoding) Jani Nikula
2025-01-11 5:26 ` Zhenyu Wang
2025-01-13 10:17 ` Zhi Wang
2025-01-11 5:12 ` [PATCH 0/3] drm/i915/gvt: Deadcoding Zhenyu Wang
2025-01-13 16:26 ` Rodrigo Vivi
2025-01-06 7:27 ` Zhenyu Wang
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=Z4A7QDtTrU6w2Yhv@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=zhenyuw.linux@gmail.com \
--cc=zhi.wang.linux@gmail.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