From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Jani Nikula <jani.nikula@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [Intel-gfx] [PULL] gvt-fixes
Date: Wed, 2 Aug 2023 08:17:08 +0100 [thread overview]
Message-ID: <f8a96212-a7f5-d5ee-1a56-e43261a34543@linux.intel.com> (raw)
In-Reply-To: <ZMnvf46JqgeIuTir@debian-scheme>
On 02/08/2023 06:54, Zhenyu Wang wrote:
>
> Hi,
>
> Here is one gvt fix for bug in AUX CH register message length get.
> Please help to pick.
Pulled, thank you!
Regards,
Tvrtko
> Thanks!
> --
> The following changes since commit e354f67733115b4453268f61e6e072e9b1ea7a2f:
>
> drm/i915: Fix an error handling path in igt_write_huge() (2023-07-25 08:38:12 +0100)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux.git tags/gvt-fixes-2023-08-02
>
> for you to fetch changes up to 46d14e17095237007b59f56aae2d81ae2dcb0f93:
>
> drm/i915/gvt: Fix bug in getting msg length in AUX CH registers handler (2023-08-01 11:21:09 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2023-08-02
>
> - Fix bug to get AUX CH register message length (Yan)
>
> ----------------------------------------------------------------
> Yan Zhao (1):
> drm/i915/gvt: Fix bug in getting msg length in AUX CH registers handler
>
> drivers/gpu/drm/i915/gvt/edid.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
next prev parent reply other threads:[~2023-08-02 7:17 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 5:54 [Intel-gfx] [PULL] gvt-fixes Zhenyu Wang
2023-08-02 7:17 ` Tvrtko Ursulin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 8:05 Zhenyu Wang
2023-01-04 11:34 ` Rodrigo Vivi
2023-01-05 0:15 ` Zhenyu Wang
2023-01-05 13:10 ` Rodrigo Vivi
2022-11-11 9:02 Zhenyu Wang
2022-11-22 5:11 ` Zhenyu Wang
2022-11-22 8:02 ` Tvrtko Ursulin
2022-08-15 2:38 Zhenyu Wang
2022-08-15 23:32 ` Rodrigo Vivi
2022-08-16 4:05 ` Zhenyu Wang
2022-08-16 4:43 ` Zhenyu Wang
2022-08-17 20:07 ` Vivi, Rodrigo
2022-08-17 21:34 ` Colin King (gmail)
2022-08-18 10:15 ` Jani Nikula
2022-08-18 14:27 ` Jani Nikula
2022-08-18 15:43 ` Vivi, Rodrigo
2022-08-22 3:00 ` Zhenyu Wang
2022-07-11 5:20 Zhenyu Wang
2022-07-12 22:24 ` Rodrigo Vivi
2021-09-18 7:11 Zhenyu Wang
2021-09-27 9:39 ` Jani Nikula
2021-08-10 5:01 Zhenyu Wang
2021-08-10 13:52 ` Rodrigo Vivi
2021-07-15 2:22 Zhenyu Wang
2021-07-15 13:56 ` Rodrigo Vivi
2021-05-19 7:49 Zhenyu Wang
2021-05-19 8:50 ` Jani Nikula
2021-04-20 2:33 Zhenyu Wang
2021-04-20 13:43 ` Rodrigo Vivi
2021-01-08 4:59 Zhenyu Wang
2021-01-11 18:13 ` Jani Nikula
2020-11-17 2:39 Zhenyu Wang
2020-11-19 6:53 ` Rodrigo Vivi
2020-10-27 3:17 Zhenyu Wang
2020-10-27 20:46 ` Rodrigo Vivi
2020-10-28 11:18 ` Vivi, Rodrigo
2020-10-30 3:09 ` Zhenyu Wang
2020-10-30 5:21 ` Zhenyu Wang
2020-10-30 22:57 ` Vivi, Rodrigo
2020-09-17 6:42 Zhenyu Wang
2020-09-22 17:27 ` Jani Nikula
2020-06-17 4:34 Zhenyu Wang
2020-06-18 12:48 ` Joonas Lahtinen
2020-06-23 3:07 ` Zhenyu Wang
2020-06-29 8:18 ` Jani Nikula
2020-05-12 2:48 Zhenyu Wang
2020-05-12 7:00 ` Rodrigo Vivi
2020-04-14 8:36 Zhenyu Wang
2020-04-14 13:11 ` Rodrigo Vivi
2020-03-10 8:09 Zhenyu Wang
2020-03-10 9:33 ` Jani Nikula
2020-02-26 10:30 Zhenyu Wang
2020-02-26 22:00 ` Jani Nikula
2020-02-12 6:59 Zhenyu Wang
2020-02-12 14:54 ` Jani Nikula
2019-12-18 5:16 Zhenyu Wang
2019-12-18 9:20 ` Joonas Lahtinen
2019-11-22 3:33 Zhenyu Wang
2019-11-22 3:33 ` Zhenyu Wang
2019-11-12 6:18 Zhenyu Wang
2019-11-12 6:18 ` Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-11-12 20:36 ` Vivi, Rodrigo
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=f8a96212-a7f5-d5ee-1a56-e43261a34543@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=zhenyuw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.