From: Jani Nikula <jani.nikula@intel.com>
To: "Manna, Animesh" <animesh.manna@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Subject: RE: [RESEND 1/4] drm/{i915, xe}/dsb: make {intel, xe}_dsb_buffer.c independent of display
Date: Fri, 28 Nov 2025 11:36:10 +0200 [thread overview]
Message-ID: <2fdae13525af9b3882bb4d7558a44d201395c472@intel.com> (raw)
In-Reply-To: <PH7PR11MB803500F399EADA5703EF35A5F9DFA@PH7PR11MB8035.namprd11.prod.outlook.com>
On Thu, 27 Nov 2025, "Manna, Animesh" <animesh.manna@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Wednesday, November 26, 2025 4:41 PM
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; ville.syrjala@linux.intel.com
>> Subject: [RESEND 1/4] drm/{i915, xe}/dsb: make {intel, xe}_dsb_buffer.c
>> independent of display
>>
>> The DSB buffer implementation is really independent of display. Pass
>> struct drm_device instead of struct intel_crtc to
>> intel_dsb_buffer_create(), and drop the intel_display_types.h include.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM.
> Reviewed-by: Animesh Manna <animesh.manna@intel.com>
Thanks, series pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-28 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 11:11 [RESEND 0/4] drm/{i915,xe}/dsb: refactor DSB buffer allocation Jani Nikula
2025-11-26 11:11 ` [RESEND 1/4] drm/{i915, xe}/dsb: make {intel, xe}_dsb_buffer.c independent of display Jani Nikula
2025-11-27 8:18 ` Manna, Animesh
2025-11-28 9:36 ` Jani Nikula [this message]
2025-11-26 11:11 ` [RESEND 2/4] drm/{i915, xe}/dsb: allocate struct intel_dsb_buffer dynamically Jani Nikula
2025-11-27 8:20 ` Manna, Animesh
2025-11-26 11:11 ` [RESEND 3/4] drm/{i915,xe}/dsb: make struct intel_dsb_buffer opaque Jani Nikula
2025-11-27 8:24 ` Manna, Animesh
2025-11-26 11:11 ` [RESEND 4/4] drm/xe/dsb: drop the unnecessary struct i915_vma Jani Nikula
2025-11-27 8:26 ` Manna, Animesh
2025-11-26 12:01 ` ✓ CI.KUnit: success for drm/{i915,xe}/dsb: refactor DSB buffer allocation (rev3) Patchwork
2025-11-26 12:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-26 14:22 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 15:36 [RESEND 0/4] drm/{i915,xe}/dsb: refactor DSB buffer allocation Jani Nikula
2025-10-22 15:36 ` [RESEND 1/4] drm/{i915, xe}/dsb: make {intel, xe}_dsb_buffer.c independent of display Jani Nikula
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=2fdae13525af9b3882bb4d7558a44d201395c472@intel.com \
--to=jani.nikula@intel.com \
--cc=animesh.manna@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