All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Sean Paul <sean@poorly.run>,
	intel-gfx@lists.freedesktop.org
Subject: [PULL] drm-intel-next-fixes
Date: Thu, 2 Apr 2020 14:30:26 -0700	[thread overview]
Message-ID: <20200402213026.GA1141017@intel.com> (raw)

Hi Dave and Daniel,

Here goes drm-intel-next-fixes-2020-04-02:

Only gvt fixes on this round:

- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)

Thanks,
Rodrigo.

The following changes since commit 2bdd4c28baff29163808677a70942de2b45f17dc:

  drm/i915/display: Fix mode private_flags comparison at atomic_check (2020-03-26 10:21:30 -0700)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2020-04-02

for you to fetch changes up to 17d0c1062a0c60e17c96538adf4a84c208930d9d:

  Merge tag 'gvt-next-fixes-2020-03-31' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2020-03-31 09:25:15 -0700)

----------------------------------------------------------------
Only gvt fixes on this round:

- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)

----------------------------------------------------------------
Rodrigo Vivi (1):
      Merge tag 'gvt-next-fixes-2020-03-31' of https://github.com/intel/gvt-linux into drm-intel-next-fixes

Tina Zhang (3):
      drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
      drm/i915/gvt: Fix display port type issue
      drm/i915/gvt: Fix klocwork issues about data size

Yan Zhao (2):
      drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
      drm/i915/gvt: do not check len & max_len for lri

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
 drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
 drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
 drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
 4 files changed, 15 insertions(+), 19 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Thu, 2 Apr 2020 14:30:26 -0700	[thread overview]
Message-ID: <20200402213026.GA1141017@intel.com> (raw)

Hi Dave and Daniel,

Here goes drm-intel-next-fixes-2020-04-02:

Only gvt fixes on this round:

- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)

Thanks,
Rodrigo.

The following changes since commit 2bdd4c28baff29163808677a70942de2b45f17dc:

  drm/i915/display: Fix mode private_flags comparison at atomic_check (2020-03-26 10:21:30 -0700)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2020-04-02

for you to fetch changes up to 17d0c1062a0c60e17c96538adf4a84c208930d9d:

  Merge tag 'gvt-next-fixes-2020-03-31' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2020-03-31 09:25:15 -0700)

----------------------------------------------------------------
Only gvt fixes on this round:

- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)

----------------------------------------------------------------
Rodrigo Vivi (1):
      Merge tag 'gvt-next-fixes-2020-03-31' of https://github.com/intel/gvt-linux into drm-intel-next-fixes

Tina Zhang (3):
      drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
      drm/i915/gvt: Fix display port type issue
      drm/i915/gvt: Fix klocwork issues about data size

Yan Zhao (2):
      drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
      drm/i915/gvt: do not check len & max_len for lri

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
 drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
 drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
 drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
 4 files changed, 15 insertions(+), 19 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2020-04-02 21:30 UTC|newest]

Thread overview: 148+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 21:30 Rodrigo Vivi [this message]
2020-04-02 21:30 ` [Intel-gfx] [PULL] drm-intel-next-fixes Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
2026-04-22  7:53 Tvrtko Ursulin
2026-04-16  6:50 Tvrtko Ursulin
2026-02-20  8:31 Joonas Lahtinen
2026-02-13 10:53 Joonas Lahtinen
2026-02-05  8:02 Joonas Lahtinen
2026-01-29  8:11 Joonas Lahtinen
2026-01-22  8:02 Joonas Lahtinen
2025-08-05  7:48 Jani Nikula
2025-06-05  8:35 Joonas Lahtinen
2025-05-28  6:56 Joonas Lahtinen
2025-05-22  6:59 Joonas Lahtinen
2025-05-15  8:27 Joonas Lahtinen
2025-03-25  9:07 Jani Nikula
2024-11-21  8:37 Tvrtko Ursulin
2024-09-26  7:45 Joonas Lahtinen
2024-09-19  9:49 Joonas Lahtinen
2024-09-12  8:59 Joonas Lahtinen
2024-07-25  7:44 Tvrtko Ursulin
2024-07-18  9:30 Tvrtko Ursulin
2024-01-19  8:30 Joonas Lahtinen
2024-01-19  8:30 ` Joonas Lahtinen
2024-01-11 10:51 Joonas Lahtinen
2024-01-11 10:51 ` Joonas Lahtinen
2023-11-08 14:04 Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06  8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21  9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20  8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24  8:44 Tvrtko Ursulin
2022-03-17  7:47 Joonas Lahtinen
2022-03-10  7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2022-01-13  9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
2021-11-09 23:17 Rodrigo Vivi
2021-08-26  9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04   ` Rodrigo Vivi
2021-07-01  8:57     ` Jani Nikula
2021-02-25 14:43 Rodrigo Vivi
2021-02-18 22:46 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10  7:31 ` Dave Airlie
2020-08-12 12:49   ` Jani Nikula
2020-06-10  9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-03-27  8:16 Rodrigo Vivi
2019-12-05  9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-14  8:52 Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-09-27 19:49 Rodrigo Vivi
2019-09-19 14:16 Rodrigo Vivi
2019-09-11 23:33 Rodrigo Vivi
2019-05-15  7:48 Joonas Lahtinen
2019-05-09 10:01 Joonas Lahtinen
2019-05-02 13:40 Joonas Lahtinen
2019-04-30  7:08 Joonas Lahtinen
2019-04-25  6:13 Joonas Lahtinen
2019-03-12 20:55 Rodrigo Vivi
2018-12-27  7:40 Jani Nikula
2018-10-25 13:18 Joonas Lahtinen
2018-10-19 10:37 Joonas Lahtinen
2018-10-19 12:34 ` Daniel Vetter
2018-10-18 16:57 Joonas Lahtinen
2018-10-18 19:32 ` Daniel Vetter
2018-10-19  6:59   ` Joonas Lahtinen
2018-10-19  7:05     ` Daniel Vetter
2018-10-19  9:41       ` Joonas Lahtinen
2018-10-04 13:37 Joonas Lahtinen
2018-08-24 21:48 Rodrigo Vivi
2018-08-16 19:03 Rodrigo Vivi
2018-08-06 23:30 Rodrigo Vivi
2018-04-19  9:30 Joonas Lahtinen
2018-03-27 14:58 Joonas Lahtinen
2018-03-22 14:35 Joonas Lahtinen
2018-02-07 20:44 Rodrigo Vivi
2018-02-02  0:45 Rodrigo Vivi
2017-11-23  9:34 Jani Nikula
2017-11-10 13:21 Jani Nikula
2017-07-11 13:07 Jani Nikula
2017-06-27  8:28 Daniel Vetter
2017-02-17  9:46 Jani Nikula
2017-02-15 14:06 Jani Nikula
2016-12-22 10:22 Jani Nikula
2016-12-07 19:45 Jani Nikula
2016-10-11 14:09 Jani Nikula
2016-08-05 13:27 Jani Nikula
2016-07-25  6:41 Daniel Vetter
2016-05-25  8:57 Jani Nikula
2016-03-16 11:04 Jani Nikula
2016-01-14 20:06 Jani Nikula
2015-11-06 13:43 Jani Nikula
2015-10-22  8:28 Daniel Vetter
2015-09-02 11:49 Jani Nikula
2015-08-28 12:44 Jani Nikula
2015-08-16 18:13 Daniel Vetter
2015-07-02 11:26 Jani Nikula
2015-06-22 10:33 Jani Nikula
2015-06-18  6:04 Jani Nikula
2015-06-19  3:48 ` Dave Airlie
2015-06-19 15:24   ` Daniel Vetter
2015-06-22  7:59     ` Ander Conselvan De Oliveira
2015-06-22  8:12       ` Jani Nikula
2015-06-22  8:13         ` Dave Airlie
2015-06-11  8:40 Jani Nikula
2015-05-29 17:39 Daniel Vetter
2015-04-24 21:46 Jani Nikula
2015-04-15 12:21 Jani Nikula
2015-02-11 11:09 Jani Nikula
2015-02-11 11:48 ` Daniel Vetter
2014-12-30 12:47 Jani Nikula
2014-12-17 12:16 Jani Nikula
2014-12-11 13:43 Jani Nikula
2014-12-04  9:56 Daniel Vetter

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=20200402213026.GA1141017@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sean@poorly.run \
    /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.