All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Jani Nikula <jani.nikula@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-next-fixes
Date: Wed, 21 Apr 2021 17:45:22 +0800	[thread overview]
Message-ID: <20210421094522.GU1551@zhen-hp.sh.intel.com> (raw)


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


Hi,

Here're queued gvt-next-fixes changes. Two ones are for code cleanup
on unused function or duplicated function call, with another one for
consistent function return type.

Thanks.
--
The following changes since commit d153e8c156dafeb847fd655f416cf81c007e8706:

  Merge tag 'drm-intel-next-fixes-2021-02-25' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2021-02-26 05:08:51 +1000)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-04-21

for you to fetch changes up to 0349ec19c484ed40dbc725820673df4d94334e8c:

  drm/i915/gvt: Remove duplicated register accessible check (2021-04-21 17:56:06 +0800)

----------------------------------------------------------------
gvt-next-fixes-2021-04-21

- Remove one unused function warning (Jiapeng)
- Fix intel_gvt_init_device() return type (Dan)
- Remove one duplicated register accessible check (Zhenyu)

----------------------------------------------------------------
Dan Carpenter (1):
      drm/i915/gvt: Fix error code in intel_gvt_init_device()

Jiapeng Chong (1):
      drm/i915/gvt: remove useless function

Zhenyu Wang (1):
      drm/i915/gvt: Remove duplicated register accessible check

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 5 -----
 drivers/gpu/drm/i915/gvt/gtt.c        | 6 ------
 drivers/gpu/drm/i915/gvt/gvt.c        | 8 ++++----
 3 files changed, 4 insertions(+), 15 deletions(-)

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

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

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

             reply	other threads:[~2021-04-21 10:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  9:45 Zhenyu Wang [this message]
2021-04-21 10:51 ` [Intel-gfx] [PULL] gvt-next-fixes Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28  7:47 Zhenyu Wang
2023-02-23  8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31  7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula
2020-04-07 23:36             ` Zhenyu Wang
2019-12-02  5:17 Zhenyu Wang
2019-12-02  5:17 ` Zhenyu Wang
2019-12-05  6:11   ` Zhenyu Wang
2019-12-05  8:14     ` Joonas Lahtinen
2019-12-05  8:49       ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` Zhenyu Wang
2019-11-20 11:25   ` Joonas Lahtinen
2019-11-20 11:25     ` Joonas Lahtinen

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=20210421094522.GU1551@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 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.