From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: chaitanya.kumar.borah@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 0/2] Fix UBSAN warning in hdcp_info
Date: Mon, 1 Apr 2024 08:31:04 +0530 [thread overview]
Message-ID: <20240401030106.274787-1-suraj.kandpal@intel.com> (raw)
This patch series fixes the UBSAN warning which gets called
when hdcp_info is invoked accompanied by some other logical fixes
required in the hdcp capability function.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Suraj Kandpal (2):
drm/i915/display: Initialize capability variables
drm/i915/hdcp: Fix get remote hdcp capability function
drivers/gpu/drm/i915/display/intel_display_debugfs.c | 2 +-
drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 5 ++++-
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.43.2
next reply other threads:[~2024-04-01 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 3:01 Suraj Kandpal [this message]
2024-04-01 3:01 ` [PATCH 1/2] drm/i915/display: Initialize capability variables Suraj Kandpal
2024-04-01 3:01 ` [PATCH 2/2] drm/i915/hdcp: Fix get remote hdcp capability function Suraj Kandpal
2024-04-01 5:42 ` Borah, Chaitanya Kumar
2024-04-01 5:56 ` Suraj Kandpal
2024-04-01 9:50 ` Borah, Chaitanya Kumar
2024-04-01 9:25 ` kernel test robot
2024-04-01 3:29 ` ✗ Fi.CI.SPARSE: warning for Fix UBSAN warning in hdcp_info (rev2) Patchwork
2024-04-01 3:39 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-01 5:26 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-01 7:35 ` ✗ Fi.CI.SPARSE: warning for Fix UBSAN warning in hdcp_info (rev3) Patchwork
2024-04-01 7:55 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-01 13:39 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-02 21:18 ` ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-03-27 4:44 [PATCH 0/2] Fix UBSAN warning in hdcp_info Suraj Kandpal
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=20240401030106.274787-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.