Quoting Wang, Zhi A (2022-03-08 12:07:04) > Which suits better for you? For me, I am OK with both. If you are not in a rush of closing the window, I can submit through drm-intel-next-fixes. I pulled this into drm-intel-next-fixes now. For future reference, let's have fixes only PRs as gvt-fixes and PRs with features as gvt-next and each as a new mail thread instead of a reply to older, so they will be easy to spot :) Regards, Joonas > > Thanks, > Zhi. > > On 3/8/22 9:56 AM, Nikula, Jani wrote: > > On Tue, 08 Mar 2022, "Wang, Zhi A" <zhi.a.wang@xxxxxxxxx> wrote: > >> Hi folks: > >> > >> Here is a new pull request of gvt-next. It contains a small patch to add the missing > >> mdev attribute name, which will be used by the middleware, like kubevirt. > > > > I'm wondering if I should pull this to drm-intel-next, which is already > > targeting v5.19, or if it should be pulled to drm-intel-next-fixes > > targeting v5.18. It does look like a fix. > > > > BR, > > Jani. > > > > > >> > >> This pull has been tested by: > >> > >> $ dim apply-pull drm-intel-next < this_email.eml > >> > >> The following changes since commit 30424ebae8df0f786835e7a31ad790fa00764f35: > >> > >> Merge tag 'drm-intel-gt-next-2022-02-17' of git://anongit.freedesktop.org/drm/drm-intel into drm-intel-next (2022-02-23 15:03:51 -0500) > >> > >> are available in the Git repository at: > >> > >> https://github.com/intel/gvt-linux tags/gvt-next-2022-03-07 > >> > >> for you to fetch changes up to 43d26c4fc6c446d766253d546f0083d78023d34a: > >> > >> drm/i915/gvt: add the missing mdev attribute "name" (2022-03-07 12:21:58 -0500) > >> > >> ---------------------------------------------------------------- > >> - add the missing attribute "name" in VFIO mdev hierarchy. > >> > >> ---------------------------------------------------------------- > >> Zhi Wang (1): > >> drm/i915/gvt: add the missing mdev attribute "name" > >> > >> drivers/gpu/drm/i915/gvt/kvmgt.c | 15 +++++++++++++++ > >> 1 file changed, 15 insertions(+) > >> > > >
