From: Jani Nikula <jani.nikula@intel.com>
To: "Wang, Zhi A" <zhi.a.wang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [GIT PULL] GVT next changes for drm-intel-next
Date: Tue, 08 Mar 2022 11:56:13 +0200 [thread overview]
Message-ID: <87wnh422f6.fsf@intel.com> (raw)
In-Reply-To: <e38f0725-6b22-8e49-b8f6-41986b0ece06@intel.com>
On Tue, 08 Mar 2022, "Wang, Zhi A" <zhi.a.wang@intel.com> 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(+)
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-03-08 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 14:43 [Intel-gfx] [GIT PULL] GVT next changes for drm-intel-next-queued Wang, Zhi A
2022-01-10 22:52 ` Vivi, Rodrigo
2022-01-11 6:08 ` Wang, Zhi A
2022-01-11 11:08 ` Wang, Zhi A
2022-01-11 14:40 ` Rodrigo Vivi
2022-01-11 18:08 ` Wang, Zhi A
2022-03-08 6:42 ` [Intel-gfx] [GIT PULL] GVT next changes for drm-intel-next Wang, Zhi A
2022-03-08 9:56 ` Jani Nikula [this message]
2022-03-08 10:07 ` Wang, Zhi A
2022-03-08 15:19 ` Joonas Lahtinen
2022-03-09 7:26 ` Wang, Zhi A
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=87wnh422f6.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=zhi.a.wang@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