public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: 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>,
	"Yuan, Hang" <hang.yuan@intel.com>
Subject: [PULL] gvt-fixes
Date: Tue, 12 Nov 2019 14:18:34 +0800	[thread overview]
Message-ID: <20191112061834.GN4196@zhen-hp.sh.intel.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]


Hi,

Here's one GVT dmabuf reference drop fix from Pan Bian.

Thanks
--
The following changes since commit ee2c5ef8a9d640ee1617ec97b84fe2f634284e51:

  drm/i915/dp: Do not switch aux to TBT mode for non-TC ports (2019-11-04 13:24:14 -0800)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-11-12

for you to fetch changes up to 41d931459b53e32c67a1f8838d1e6826a69ee745:

  drm/i915/gvt: fix dropping obj reference twice (2019-11-08 11:04:07 +0800)

----------------------------------------------------------------
gvt-fixes-2019-11-12

- Fix dmabuf reference drop (Pan)

----------------------------------------------------------------
Pan Bian (1):
      drm/i915/gvt: fix dropping obj reference twice

 drivers/gpu/drm/i915/gvt/dmabuf.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: 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>,
	"Yuan, Hang" <hang.yuan@intel.com>
Subject: [Intel-gfx] [PULL] gvt-fixes
Date: Tue, 12 Nov 2019 14:18:34 +0800	[thread overview]
Message-ID: <20191112061834.GN4196@zhen-hp.sh.intel.com> (raw)
Message-ID: <20191112061834.CDEzk6oSmKesYDGkNGNLHXGaSB4uoMQi-ILWwBX6Bso@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]


Hi,

Here's one GVT dmabuf reference drop fix from Pan Bian.

Thanks
--
The following changes since commit ee2c5ef8a9d640ee1617ec97b84fe2f634284e51:

  drm/i915/dp: Do not switch aux to TBT mode for non-TC ports (2019-11-04 13:24:14 -0800)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-11-12

for you to fetch changes up to 41d931459b53e32c67a1f8838d1e6826a69ee745:

  drm/i915/gvt: fix dropping obj reference twice (2019-11-08 11:04:07 +0800)

----------------------------------------------------------------
gvt-fixes-2019-11-12

- Fix dmabuf reference drop (Pan)

----------------------------------------------------------------
Pan Bian (1):
      drm/i915/gvt: fix dropping obj reference twice

 drivers/gpu/drm/i915/gvt/dmabuf.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-11-12  6:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12  6:18 Zhenyu Wang [this message]
2019-11-12  6:18 ` [Intel-gfx] [PULL] gvt-fixes Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-11-12 20:36   ` [Intel-gfx] " Vivi, Rodrigo
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31  9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05  3:21   ` Zhenyu Wang
2019-11-22  3:33 Zhenyu Wang
2019-08-13  9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-07-23  9:29 Zhenyu Wang
2019-07-29  3:33 ` Zhenyu Wang
2019-07-29 11:05   ` Jani Nikula
2019-07-30  7:00     ` Zhenyu Wang
2019-07-30  8:33       ` Jani Nikula
2019-06-19  6:22 Zhenyu Wang
2019-06-19  7:56 ` Jani Nikula
2019-06-05  8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-05-29  9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30  3:41   ` Zhenyu Wang
2019-05-31  8:16     ` Joonas Lahtinen
2019-05-21  6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11  6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-04-02  9:40 Zhenyu Wang
2019-04-04  0:12 ` Rodrigo Vivi
2019-04-04  0:32   ` Zhenyu Wang
2019-04-04  1:03     ` Rodrigo Vivi
2019-04-04  0:39   ` Zhenyu Wang
2019-03-21  3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24  5:48 Zhenyu Wang
2019-01-31  9:45 ` Jani Nikula

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=20191112061834.GN4196@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=hang.yuan@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=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