From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dim-tools@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Dave Airlie <airlied@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Fri, 10 Nov 2023 16:48:18 +0100 [thread overview]
Message-ID: <ZU5QwmPKF7pelDVF@phenom.ffwll.local> (raw)
In-Reply-To: <878r78xrxd.fsf@intel.com>
On Wed, Nov 08, 2023 at 04:04:14PM +0200, Jani Nikula wrote:
>
> Hi Dave & Daniel -
>
> I see Dave already sent the pull request for v6.7-rc1 fixes, but here's
> some more.
>
> drm-intel-next-fixes-2023-11-08:
> drm/i915 fixes for v6.7-rc1:
> - Fix null dereference when perf interface is not available
> - Fix a -Wstringop-overflow warning
> - Fix a -Wformat-truncation warning in intel_tc_port_init
> - Flush WC GGTT only on required platforms
> - Fix MTL HBR3 rate support on C10 phy and eDP
> - Fix MTL notify_guc for multi-GT
> - Bump GLK CDCLK frequency when driving multiple pipes
> - Fix potential spectre vulnerability
>
> BR,
> Jani.
>
> The following changes since commit 5258dfd4a6adb5f45f046b0dd2e73c680f880d9d:
>
> usb: typec: altmodes/displayport: fixup drm internal api change vs new user. (2023-10-27 07:55:41 +1000)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2023-11-08
Pulled into drm-next, thanks.
-Sima
>
> for you to fetch changes up to 9506fba463fcbdf8c8b7af3ec9ee34360df843fe:
>
> drm/i915/tc: Fix -Wformat-truncation in intel_tc_port_init (2023-11-06 14:42:58 +0200)
>
> ----------------------------------------------------------------
> drm/i915 fixes for v6.7-rc1:
> - Fix null dereference when perf interface is not available
> - Fix a -Wstringop-overflow warning
> - Fix a -Wformat-truncation warning in intel_tc_port_init
> - Flush WC GGTT only on required platforms
> - Fix MTL HBR3 rate support on C10 phy and eDP
> - Fix MTL notify_guc for multi-GT
> - Bump GLK CDCLK frequency when driving multiple pipes
> - Fix potential spectre vulnerability
>
> ----------------------------------------------------------------
> Arnd Bergmann (1):
> drm/i915/mtl: avoid stringop-overflow warning
>
> Chaitanya Kumar Borah (1):
> drm/i915/mtl: Support HBR3 rate with C10 phy and eDP in MTL
>
> Harshit Mogalapalli (1):
> i915/perf: Fix NULL deref bugs with drm_dbg() calls
>
> Kunwu Chan (1):
> drm/i915: Fix potential spectre vulnerability
>
> Nirmoy Das (3):
> drm/i915: Flush WC GGTT only on required platforms
> drm/i915/mtl: Apply notify_guc to all GTs
> drm/i915/tc: Fix -Wformat-truncation in intel_tc_port_init
>
> Ville Syrjälä (1):
> drm/i915: Bump GLK CDCLK frequency when driving multiple pipes
>
> drivers/gpu/drm/i915/display/intel_cdclk.c | 12 ++++++++++
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> drivers/gpu/drm/i915/display/intel_tc.c | 11 ++++++---
> drivers/gpu/drm/i915/gem/i915_gem_context.c | 1 +
> drivers/gpu/drm/i915/gt/intel_ggtt.c | 35 ++++++++++++++++++++---------
> drivers/gpu/drm/i915/gt/intel_rc6.c | 16 ++++++++-----
> drivers/gpu/drm/i915/i915_debugfs_params.c | 9 +++++---
> drivers/gpu/drm/i915/i915_perf.c | 15 +++----------
> 8 files changed, 65 insertions(+), 36 deletions(-)
>
> --
> Jani Nikula, Intel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-11-10 15:48 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 14:04 [Intel-gfx] [PULL] drm-intel-next-fixes Jani Nikula
2023-11-10 15:48 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
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-08-05 8:46 ` Mauro Carvalho Chehab
2022-08-05 14:39 ` Rodrigo Vivi
2022-08-05 15:25 ` Mauro Carvalho Chehab
2022-08-05 20:39 ` 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-07-01 19:30 ` Rodrigo Vivi
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-04-02 21:30 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-28 14:15 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-22 15:55 ` [Intel-gfx] " Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-20 20:40 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-22 12:08 ` [Intel-gfx] " Joonas Lahtinen
2019-11-14 8:52 Joonas Lahtinen
2019-11-14 8:52 ` [Intel-gfx] " Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-11-07 14:50 ` [Intel-gfx] " 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=ZU5QwmPKF7pelDVF@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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=jani.nikula@intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).