All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten@lankhorst.se>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [PATCH] drm/{i915,xe}/fbdev: add intel_fbdev_fb_pitch_align()
Date: Thu, 16 Oct 2025 18:36:28 +0300	[thread overview]
Message-ID: <dcf1a7429a0cc7b60cfc315ced367e814a38e45e@intel.com> (raw)
In-Reply-To: <c7412925-3ea5-4541-9397-0d8c84f747c4@lankhorst.se>

On Thu, 16 Oct 2025, Maarten Lankhorst <maarten@lankhorst.se> wrote:
> Seems to me like this should be fixed at the xe level, not worked
> around at the display level?

Completely agreed.

> It shouldn't be too hard to look at what's going wrong and fix it at
> the right level instead of not even attempting to look at it.

Who's going to do it? I'm frankly clueless about what's going on, and I
don't have the means to reproduce the issue.

At the same time the bisect points at my commit, so here we are. :/


BR,
Jani.


-- 
Jani Nikula, Intel

      reply	other threads:[~2025-10-16 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 11:19 [PATCH] drm/{i915,xe}/fbdev: add intel_fbdev_fb_pitch_align() Jani Nikula
2025-10-15 13:02 ` ✓ i915.CI.BAT: success for " Patchwork
2025-10-15 18:13 ` ✗ i915.CI.Full: failure " Patchwork
2025-10-15 18:19 ` [PATCH] " Ville Syrjälä
2025-10-15 18:20 ` ✗ CI.checkpatch: warning for " Patchwork
2025-10-15 18:21 ` ✓ CI.KUnit: success " Patchwork
2025-10-15 19:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-16  6:27 ` ✓ Xe.CI.Full: " Patchwork
2025-10-16 13:42 ` [PATCH] " Maarten Lankhorst
2025-10-16 15:36   ` 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=dcf1a7429a0cc7b60cfc315ced367e814a38e45e@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@intel.com \
    --cc=maarten@lankhorst.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.