From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/{i915, xe}/display: make pxp key check part of bo interface
Date: Tue, 02 Dec 2025 12:15:44 +0200 [thread overview]
Message-ID: <ff328334844100153ff2c3d2f6c6710de01a8136@intel.com> (raw)
In-Reply-To: <aS3RwWnBy2nHtLLo@intel.com>
On Mon, 01 Dec 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Mon, Dec 01, 2025 at 07:27:30PM +0200, Jani Nikula wrote:
>> Add intel_bo_key_check() next to intel_bo_is_protected() where it feels
>> like it belongs, and drop the extra pxp compat header.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks, pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-02 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 17:27 [PATCH] drm/{i915, xe}/display: make pxp key check part of bo interface Jani Nikula
2025-12-01 17:34 ` Rodrigo Vivi
2025-12-02 10:15 ` Jani Nikula [this message]
2025-12-01 22:27 ` ✗ CI.checkpatch: warning for " Patchwork
2025-12-01 22:29 ` ✓ CI.KUnit: success " Patchwork
2025-12-01 23:18 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-02 2:38 ` ✗ Xe.CI.Full: failure " Patchwork
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=ff328334844100153ff2c3d2f6c6710de01a8136@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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