From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <dri-devel@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <airlied@gmail.com>,
<daniel.vetter@ffwll.ch>, <lucas.demarchi@intel.com>,
<ogabbay@kernel.org>, <thomas.hellstrom@linux.intel.com>
Subject: [PULL] drm-xe-next-fixes
Date: Tue, 26 Dec 2023 13:27:24 -0500 [thread overview]
Message-ID: <ZYsbDPBLUiqDevLt@intel.com> (raw)
Hi Dave and Sima,
Here goes the fixes that I had promised last week.
With these in place we should be good now with the all yes config W=1
and different compilers.
Thanks for already include that one that disables the 32-bit. I had
just noticed when I was trying to cherry-pick it to the -next-fixes branch.
Thanks,
Rodrigo.
The following changes since commit 92242716ee92d2aa3c38c736b53d8910d443566d:
Merge tag 'drm-habanalabs-next-2023-12-19' of https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux into drm-next (2023-12-22 14:52:04 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2023-12-26
for you to fetch changes up to 315acff5196f4e2f84a2a2d093000e0c6b0b4d1c:
drm/xe: Fix warning on impossible condition (2023-12-26 12:53:26 -0500)
----------------------------------------------------------------
- Fix couple unfined behavior cases to calm UBSAN and clang (Matt Brost, Lucas)
----------------------------------------------------------------
Lucas De Marchi (1):
drm/xe: Fix warning on impossible condition
Matthew Brost (1):
drm/xe: Fix UBSAN splat in add_preempt_fences()
drivers/gpu/drm/xe/xe_vm.c | 3 +++
drivers/gpu/drm/xe/xe_wait_user_fence.c | 1 +
2 files changed, 4 insertions(+)
next reply other threads:[~2023-12-26 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 18:27 Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 10:22 [PULL] drm-xe-next-fixes Thomas Hellström
2024-03-04 16:00 Lucas De Marchi
2024-03-15 4:14 Lucas De Marchi
2024-05-02 14:26 Thomas Hellstrom
2024-05-09 16:35 Thomas Hellstrom
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=ZYsbDPBLUiqDevLt@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=ogabbay@kernel.org \
--cc=thomas.hellstrom@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).