From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Arun R Murthy <arun.r.murthy@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, Dave Airlie <airlied@gmail.com>,
Simona Vetter <simona.vetter@ffwll.ch>
Cc: chaitanya.kumar.borah@intel.com, ville.syrjala@intel.com,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Naveen Kumar" <naveen1.kumar@intel.com>,
"Suraj Kandpal" <suraj.kandpal@intel.com>
Subject: Re: [PATCH RESEND v13 0/5] Expose modifiers/formats supported by async flips
Date: Fri, 9 May 2025 13:55:30 +0200 [thread overview]
Message-ID: <98c8bb9b-fb51-48ef-9b8a-51f69764c535@linux.intel.com> (raw)
In-Reply-To: <87plgimdme.fsf@intel.com>
Hey,
This would be a question for Dave and Simona,
I don't mind sending another pull request, but it's up to them on how to handle it.
Best regards,
~Maarten
On 2025-05-09 09:45, Jani Nikula wrote:
> On Mon, 07 Apr 2025, Arun R Murthy <arun.r.murthy@intel.com> wrote:
>> Arun R Murthy (5):
>> drm/i915/display: Populate list of async supported formats/modifiers
>> drm/i915/display: Add function for format_mod_supported_async
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> for merging these via drm-misc-next.
>
> Maarten, I see that you did the final pull drm-misc-next pull request
> yesterday... would you consider doing one more once this is merged so we
> can get back in sync faster?
>
> Thanks,
> Jani.
>
>
prev parent reply other threads:[~2025-05-09 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 5:43 [PATCH RESEND v13 0/5] Expose modifiers/formats supported by async flips Arun R Murthy
2025-04-07 5:43 ` [PATCH RESEND v13 1/5] drm/plane: Add new plane property IN_FORMATS_ASYNC Arun R Murthy
2025-04-07 5:43 ` [PATCH RESEND v13 2/5] drm/plane: modify create_in_formats to acommodate async Arun R Murthy
2025-04-07 5:43 ` [PATCH RESEND v13 3/5] drm/i915/display: Acomodate format check in intel_plane_can_async_flip() Arun R Murthy
2025-04-07 5:43 ` [PATCH RESEND v13 4/5] drm/i915/display: Add i915 hook for format_mod_supported_async Arun R Murthy
2025-04-07 5:43 ` [PATCH RESEND v13 5/5] drm/i915/display: Indexed 8bit format does not support async flip Arun R Murthy
2025-04-07 13:35 ` ✓ CI.Patch_applied: success for Expose modifiers/formats supported by async flips (rev16) Patchwork
2025-04-07 13:36 ` ✓ CI.checkpatch: " Patchwork
2025-04-07 13:37 ` ✓ CI.KUnit: " Patchwork
2025-04-07 13:40 ` ✗ CI.Build: failure " Patchwork
2025-04-16 6:21 ` [PATCH RESEND v13 0/5] Expose modifiers/formats supported by async flips Borah, Chaitanya Kumar
2025-04-23 15:21 ` Alex Deucher
2025-05-08 13:38 ` Murthy, Arun R
2025-05-08 14:43 ` Harry Wentland
2025-05-09 7:45 ` Jani Nikula
2025-05-09 7:49 ` Jani Nikula
2025-05-09 10:08 ` Kandpal, Suraj
2025-05-09 11:55 ` Maarten Lankhorst [this message]
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=98c8bb9b-fb51-48ef-9b8a-51f69764c535@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=airlied@gmail.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=jani.nikula@linux.intel.com \
--cc=naveen1.kumar@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=suraj.kandpal@intel.com \
--cc=ville.syrjala@intel.com \
--cc=ville.syrjala@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