From: Jani Nikula <jani.nikula@intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <dev@lankhorst.se>
Subject: Re: [PATCH 0/8] drm/{i915,xe}/panic: refactor framebuffer allocation etc.
Date: Mon, 08 Sep 2025 14:29:37 +0300 [thread overview]
Message-ID: <9663f4922edbf964abf49c6790444616917d52f3@intel.com> (raw)
In-Reply-To: <d34b0f39-2cea-4153-b019-163520f4e486@redhat.com>
On Thu, 04 Sep 2025, Jocelyn Falempe <jfalempe@redhat.com> wrote:
> On 02/09/2025 19:51, Jani Nikula wrote:
>> Split out intel_panic functionality separate from intel_bo abstraction,
>> and lift the framebuffer allocation back to where it belongs in
>> intel_fb.c.
>>
>> There's more that should be improved, ideally making struct
>> intel_framebuffer opaque towards i915 and xe, but this already goes
>> along way in adjusting where the abstractions should happen.
>
> Thanks for this series, this makes sense, and moving the panic part to
> intel_panic.c is a good idea.
>
> I think this may conflict with
> https://patchwork.freedesktop.org/series/150887/ but that should be
> trivial to resolve.
Thanks for the review. It seems to me that's much easier to rebase than
this series, and moves further away from the goals here, so I've opted
to push this one.
BR,
Jani.
> For the whole series:
> Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
>
> Best regards,
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-09-08 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 17:51 [PATCH 0/8] drm/{i915, xe}/panic: refactor framebuffer allocation etc Jani Nikula
2025-09-02 17:51 ` [PATCH 1/8] drm/i915/fb: add intel_framebuffer_alloc() Jani Nikula
2025-09-02 17:51 ` [PATCH 2/8] drm/{i915,xe}/panic: split out intel_panic.[ch] Jani Nikula
2025-09-02 17:51 ` [PATCH 3/8] drm/{i915, xe}/panic: rename intel_bo_panic_*() to intel_panic_*() Jani Nikula
2025-09-02 17:51 ` [PATCH 4/8] drm/{i915, xe}/fb: add panic pointer member to struct intel_framebuffer Jani Nikula
2025-09-02 17:51 ` [PATCH 5/8] drm/{i915, xe}/panic: rename struct {i915, xe}_panic_data to struct intel_panic Jani Nikula
2025-09-02 17:51 ` [PATCH 6/8] drm/{i915, xe}/panic: move framebuffer allocation where it belongs Jani Nikula
2025-10-01 15:04 ` [PATCH 6/8] drm/{i915,xe}/panic: " Jani Nikula
2025-10-01 16:37 ` Ville Syrjälä
2025-10-01 17:28 ` Jani Nikula
2025-10-01 17:43 ` Ville Syrjälä
2025-09-02 17:51 ` [PATCH 7/8] drm/{i915, xe}/panic: convert intel_panic_finish() to struct intel_panic Jani Nikula
2025-09-02 17:51 ` [PATCH 8/8] drm/{i915, xe}/panic: pass struct intel_panic to intel_panic_setup() Jani Nikula
2025-09-02 20:51 ` ✓ i915.CI.BAT: success for drm/{i915, xe}/panic: refactor framebuffer allocation etc Patchwork
2025-09-03 7:05 ` ✗ i915.CI.Full: failure " Patchwork
2025-09-04 11:46 ` [PATCH 0/8] " Jocelyn Falempe
2025-09-08 11:29 ` Jani Nikula [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=9663f4922edbf964abf49c6790444616917d52f3@intel.com \
--to=jani.nikula@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jfalempe@redhat.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