From: Jani Nikula <jani.nikula@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [Intel-xe] [PATCH 0/2] Backport set frontbuffer return value check
Date: Fri, 29 Sep 2023 14:05:02 +0300 [thread overview]
Message-ID: <87lecpi6jl.fsf@intel.com> (raw)
In-Reply-To: <20230929105030.1132290-1-jouni.hogander@intel.com>
On Fri, 29 Sep 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> This patch set is backporting set frontbuffer value check patch from
> upstream and reverting similar patch we have in drm-xe-next branch.
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> Cc: Jani Nikula <jani.nikula@intel.com>
>
> Jouni Högander (2):
> Revert "drm/i915: Ignore set frontbuffer return value on release"
> drm/i915: Warn on if set frontbuffer return value is not NULL on
> release
>
> drivers/gpu/drm/i915/display/intel_frontbuffer.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-29 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 10:50 [Intel-xe] [PATCH 0/2] Backport set frontbuffer return value check Jouni Högander
2023-09-29 10:50 ` [Intel-xe] [PATCH 1/2] Revert "drm/i915: Ignore set frontbuffer return value on release" Jouni Högander
2023-09-29 10:50 ` [Intel-xe] [PATCH 2/2] drm/i915: Warn on if set frontbuffer return value is not NULL on release Jouni Högander
2023-09-29 10:59 ` [Intel-xe] ✓ CI.Patch_applied: success for Backport set frontbuffer return value check Patchwork
2023-09-29 10:59 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-29 11:01 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-29 11:05 ` Jani Nikula [this message]
2023-09-29 11:08 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-29 11:08 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-29 11:09 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-29 11:42 ` [Intel-xe] ✓ CI.BAT: success " 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=87lecpi6jl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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