From: Zhi Wang <zhiwang@kernel.org>
To: Zhenyu Wang <zhenyuw.linux@gmail.com>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
zhiyuan.lv@intel.com, james.y.wu@intel.com, kevin.tian@intel.com,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
zhi.wang.linux@gmail.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,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: GVT-g status (was: Re: [PATCH 0/3] drm/i915/gvt: Deadcoding)
Date: Mon, 13 Jan 2025 12:17:49 +0200 [thread overview]
Message-ID: <20250113121749.00006dec.zhiwang@kernel.org> (raw)
In-Reply-To: <Z4IA6XtXX-e0Du-6@dell-wzy>
On Sat, 11 Jan 2025 14:26:01 +0900
Zhenyu Wang <zhenyuw.linux@gmail.com> wrote:
> On Fri, Jan 10, 2025 at 12:49:27PM +0200, Jani Nikula wrote:
> > On Thu, 09 Jan 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > > 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?
> >
> > AFAICT the last gvt-next pull request was more than two years ago
> > and gvt-fixes slightly less than one year ago.
> >
> > There's a single cleanup commit in gvt-next applied two years ago
> > for which there hasn't been a pull request.
> >
> > The GVT github page [1] says, "This repository has been archived by
> > the owner on Oct 3, 2024. It is now read-only." The intel-gvt-dev
> > mailing list [2] appears to be mostly spam.
> >
> > Seems to me something like this would be appropriate:
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 1c3eab5d2b1a..161206fdaf05 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11557,11 +11557,10 @@ F: drivers/gpio/gpio-tangier.h
> > INTEL GVT-g DRIVERS (Intel GPU Virtualization)
> > M: Zhenyu Wang <zhenyuw.linux@gmail.com>
> > M: Zhi Wang <zhi.wang.linux@gmail.com>
> > -L: intel-gvt-dev@lists.freedesktop.org
> > L: intel-gfx@lists.freedesktop.org
> > -S: Supported
> > +S: Maintained
> > W: https://github.com/intel/gvt-linux/wiki
> > -T: git https://github.com/intel/gvt-linux.git
> > +T: git https://gitlab.freedesktop.org/drm/i915/kernel.git
> > F: drivers/gpu/drm/i915/gvt/
> >
>
> Looks fine with me.
>
> Acked-by: Zhenyu Wang <zhenyuw.linux@gmail.com>
>
> > INTEL HID EVENT DRIVER
> >
> > But I don't think it would be far from the truth to have "S: Odd
> > Fixes" either. And the extreme would be to just remove the whole
> > maintainers entry and have it fall back to the i915 entry.
> >
> > Thoughts?
> >
>
> When I left Intel, I have raised similar question to manager or
> related people to see their ideas on how to keep GVT-g maintenance
> work for upstream, but I didn't get real answers before my last day
> at Intel...So still cc some intel gvt related people to double
> confirm.
>
> For me, it's fine to remove the maintainer entry maybe only keep as
> reviewer?
>
> Thanks to raise up this issue, Jani!
>
Works for me as well. I am mostly doing this as a hobby on my Skylake
desktop in my spare time.
Z.
next prev parent reply other threads:[~2025-01-13 10:17 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
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 [this message]
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=20250113121749.00006dec.zhiwang@kernel.org \
--to=zhiwang@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=james.y.wu@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=zhenyuw.linux@gmail.com \
--cc=zhi.wang.linux@gmail.com \
--cc=zhiyuan.lv@intel.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