From: Thomas Hellstrom <thomas.hellstrom@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-xe-next-fixes
Date: Wed, 28 May 2025 18:21:54 +0200 [thread overview]
Message-ID: <aDc4Is-sQb3DPGO5@fedora> (raw)
Hi Dave, Simona
Two documentation fixes this week.
Thanks,
Thomas
drm-xe-next-fixes-2025-05-28:
Driver Changes:
- Two documentation fixes (Rodrigo)
The following changes since commit 879ede53958f7bab79a88888f77e0ca91f0f77da:
drm/xe: Default auto_link_downgrade status to false (2025-05-23 09:41:06 +0200)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2025-05-28
for you to fetch changes up to 40493d97b329f8185c0f04dc0ef2b9ffc58e7f3b:
drm/xe: Add missing documentation of rpa_freq (2025-05-28 17:23:13 +0200)
----------------------------------------------------------------
Driver Changes:
- Two documentation fixes (Rodrigo)
----------------------------------------------------------------
Rodrigo Vivi (2):
drm/xe: Make xe_gt_freq part of the Documentation
drm/xe: Add missing documentation of rpa_freq
Documentation/gpu/xe/index.rst | 1 +
Documentation/gpu/xe/xe_gt_freq.rst | 14 ++++++++++++++
drivers/gpu/drm/xe/xe_gt_freq.c | 5 +++++
3 files changed, 20 insertions(+)
create mode 100644 Documentation/gpu/xe/xe_gt_freq.rst
next reply other threads:[~2025-05-28 16:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 16:21 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-06 13:24 [PULL] drm-xe-next-fixes Rodrigo Vivi
2025-07-31 19:46 Rodrigo Vivi
2025-06-05 19:07 Thomas Hellstrom
2025-05-23 8:25 Thomas Hellstrom
2025-03-27 15:14 Lucas De Marchi
2025-03-13 4:41 Lucas De Marchi
2024-11-28 15:39 Thomas Hellstrom
2024-11-21 19:39 Thomas Hellstrom
2024-11-15 11:10 Thomas Hellstrom
2024-09-20 2:56 Lucas De Marchi
2024-09-20 3:14 ` Lucas De Marchi
2024-09-12 23:23 Lucas De Marchi
2024-07-18 15:51 Rodrigo Vivi
2024-07-09 21:31 Rodrigo Vivi
2024-07-10 19:42 ` Lucas De Marchi
2024-07-10 20:45 ` Rodrigo Vivi
2024-05-09 16:35 Thomas Hellstrom
2024-05-02 14:26 Thomas Hellstrom
2024-03-15 4:14 Lucas De Marchi
2024-03-04 16:00 Lucas De Marchi
2024-01-16 10:22 Thomas Hellström
2023-12-26 18:27 Rodrigo Vivi
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=aDc4Is-sQb3DPGO5@fedora \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=tursulin@ursulin.net \
--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).