From: Lucas De Marchi <lucas.demarchi@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 0/9] drm/i915: Plane fb refactoring
Date: Sat, 11 May 2024 14:00:17 -0500 [thread overview]
Message-ID: <utvoij55zjtp6hujxl3luidq7whrjvte64wv5r46pib6xkspvn@asptafecjvyf> (raw)
In-Reply-To: <Zj5Rc5cMrcfnV-aI@intel.com>
On Fri, May 10, 2024 at 07:55:15PM GMT, Ville Syrjälä wrote:
>On Mon, May 06, 2024 at 03:57:09PM +0300, Ville Syrjala wrote:
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>> A bit of cleanup/refactoring around plane fb stuff.
>> This is mainly prep work for a slightly bigger rework
>> of alignment handling.
>>
>> Ville Syrjälä (9):
>> drm/i915: Split gen2 vs. gen3 .max_stride()
>> drm/i915: Clean up skl+ plane stride limits
>> drm/i915: Drop 'uses_fence' parameter from intel_pin_fb_obj_dpt()
>> drm/i915: Extract intel_plane_needs_physical()
>> drm/i915: Polish types in fb calculations
>
>Pushed up to here. Thanks for the review.
>
>> drm/i915: Constify 'fb' in during pinning
>> drm/i915: Change intel_fbdev_fb_alloc() reuturn type
>> drm/i915: Cleanup fbdev fb setup
>> drm/i915: Rename the fb pinning functions to indicate the address
>> space
>
>Some of the rest touch xe as well.
>
>Lucas, can you toss me an ack to merge via drm-intel-next?
Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
thanks
Lucas De Marchi
prev parent reply other threads:[~2024-05-11 19:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 12:57 [PATCH 0/9] drm/i915: Plane fb refactoring Ville Syrjala
2024-05-06 12:57 ` [PATCH 1/9] drm/i915: Split gen2 vs. gen3 .max_stride() Ville Syrjala
2024-05-06 13:57 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 2/9] drm/i915: Clean up skl+ plane stride limits Ville Syrjala
2024-05-06 14:03 ` Jani Nikula
2024-05-06 16:38 ` Ville Syrjälä
2024-05-07 9:02 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 3/9] drm/i915: Drop 'uses_fence' parameter from intel_pin_fb_obj_dpt() Ville Syrjala
2024-05-06 14:04 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 4/9] drm/i915: Extract intel_plane_needs_physical() Ville Syrjala
2024-05-06 14:05 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 5/9] drm/i915: Polish types in fb calculations Ville Syrjala
2024-05-06 14:07 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 6/9] drm/i915: Constify 'fb' in during pinning Ville Syrjala
2024-05-06 14:11 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 7/9] drm/i915: Change intel_fbdev_fb_alloc() reuturn type Ville Syrjala
2024-05-06 14:16 ` Jani Nikula
2024-05-06 16:51 ` Ville Syrjälä
2024-05-06 18:19 ` Ville Syrjälä
2024-05-10 10:22 ` [PATCH v2 7/9] drm/i915: Change intel_fbdev_fb_alloc() return type Ville Syrjala
2024-05-10 11:30 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 8/9] drm/i915: Cleanup fbdev fb setup Ville Syrjala
2024-05-10 10:22 ` [PATCH v2 " Ville Syrjala
2024-05-10 11:32 ` Jani Nikula
2024-05-06 12:57 ` [PATCH 9/9] drm/i915: Rename the fb pinning functions to indicate the address space Ville Syrjala
2024-05-10 11:35 ` Jani Nikula
2024-05-06 13:02 ` ✓ CI.Patch_applied: success for drm/i915: Plane fb refactoring Patchwork
2024-05-06 13:03 ` ✓ CI.checkpatch: " Patchwork
2024-05-06 13:03 ` ✓ CI.KUnit: " Patchwork
2024-05-06 13:15 ` ✓ CI.Build: " Patchwork
2024-05-06 13:18 ` ✓ CI.Hooks: " Patchwork
2024-05-06 13:19 ` ✗ CI.checksparse: warning " Patchwork
2024-05-06 13:53 ` ✓ CI.BAT: success " Patchwork
2024-05-06 15:07 ` ✓ CI.FULL: " Patchwork
2024-05-10 10:52 ` ✓ CI.Patch_applied: success for drm/i915: Plane fb refactoring (rev3) Patchwork
2024-05-10 10:53 ` ✓ CI.checkpatch: " Patchwork
2024-05-10 10:55 ` ✓ CI.KUnit: " Patchwork
2024-05-10 11:07 ` ✓ CI.Build: " Patchwork
2024-05-10 11:10 ` ✓ CI.Hooks: " Patchwork
2024-05-10 11:11 ` ✗ CI.checksparse: warning " Patchwork
2024-05-10 11:43 ` ✗ CI.BAT: failure " Patchwork
2024-05-10 13:54 ` ✓ CI.FULL: success " Patchwork
2024-05-10 16:55 ` [PATCH 0/9] drm/i915: Plane fb refactoring Ville Syrjälä
2024-05-11 19:00 ` Lucas De Marchi [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=utvoij55zjtp6hujxl3luidq7whrjvte64wv5r46pib6xkspvn@asptafecjvyf \
--to=lucas.demarchi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).