Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>,
	<dri-devel@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: <chaitanya.kumar.borah@intel.com>,
	Naveen Kumar <naveen1.kumar@intel.com>
Subject: Re: [PATCH v5 3/3] drm/i915/display: Add i915 hook for format_mod_supported_async
Date: Tue, 18 Feb 2025 14:50:24 +0000	[thread overview]
Message-ID: <D7VNLYP11ULY.1J6RH9V7LJV46@intel.com> (raw)
In-Reply-To: <20250218-asyn-v5-3-7ac5ac4abd4a@intel.com>

On Tue Feb 18, 2025 at 9:02 AM UTC, Arun R Murthy wrote:
> Hook up the newly added plane function pointer
> format_mod_supported_async to populate the modifiers/formats supported
> by asynchronous flips.
>
> v5: Correct the if condition for modifier support check (Chaitanya)
>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> Tested-by: Naveen Kumar <naveen1.kumar@intel.com>

LGTM
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>

-- 
Best regards,
Sebastian


  parent reply	other threads:[~2025-02-18 14:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  9:02 [PATCH v5 0/3] Expose modifiers/formats supported by async flips Arun R Murthy
2025-02-18  9:02 ` [PATCH v5 1/3] drm/plane: Add new plane property IN_FORMATS_ASYNC Arun R Murthy
2025-02-18  9:02 ` [PATCH v5 2/3] drm/plane: modify create_in_formats to accommodate async Arun R Murthy
2025-02-18  9:02 ` [PATCH v5 3/3] drm/i915/display: Add i915 hook for format_mod_supported_async Arun R Murthy
2025-02-18 11:46   ` Jani Nikula
2025-02-18 14:50   ` Sebastian Brzezinka [this message]
2025-02-18 10:17 ` ✓ CI.Patch_applied: success for Expose modifiers/formats supported by async flips (rev5) Patchwork
2025-02-18 10:17 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-18 10:18 ` ✓ CI.KUnit: success " Patchwork
2025-02-18 10:35 ` ✓ CI.Build: " Patchwork
2025-02-18 10:37 ` ✓ CI.Hooks: " Patchwork
2025-02-18 10:39 ` ✗ CI.checksparse: warning " Patchwork
2025-02-19  7:29 ` ✓ CI.Patch_applied: success for Expose modifiers/formats supported by async flips (rev6) Patchwork
2025-02-19  7:29 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-19  7:30 ` ✓ CI.KUnit: success " Patchwork
2025-02-19  7:47 ` ✓ CI.Build: " Patchwork
2025-02-19  7:49 ` ✓ CI.Hooks: " Patchwork
2025-02-19  7:51 ` ✗ CI.checksparse: warning " Patchwork
2025-02-19  8:10 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-20  4:09 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-20  8:24 ` ✗ Xe.CI.Full: failure for Expose modifiers/formats supported by async flips (rev5) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-02-12 16:18 [PATCH v5 0/3] Expose modifiers/formats supported by async flips Arun R Murthy
2025-02-12 16:18 ` [PATCH v5 3/3] drm/i915/display: Add i915 hook for format_mod_supported_async Arun R Murthy
2025-02-17  5:28   ` Borah, Chaitanya Kumar

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=D7VNLYP11ULY.1J6RH9V7LJV46@intel.com \
    --to=sebastian.brzezinka@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=naveen1.kumar@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