mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "José Expósito" <jose.exposito89@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, simona@ffwll.ch, lumag@kernel.org,
	cristian.ciocaltea@collabora.com, gcarlos@disroot.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/tests: Fix drm_test_fb_xrgb8888_to_xrgb2101010() on big-endian
Date: Mon, 11 Aug 2025 12:24:41 +0200	[thread overview]
Message-ID: <aJnE6Uu_WutFA06X@fedora> (raw)
In-Reply-To: <9467c5f1-fb70-4698-a611-80f9be499b22@suse.de>

Hi Thomas,

On Mon, Jun 30, 2025 at 01:37:58PM +0200, Thomas Zimmermann wrote:
> 
> 
> Am 30.06.25 um 11:00 schrieb José Expósito:
> > Fix failures on big-endian architectures on tests cases
> > single_pixel_source_buffer, single_pixel_clip_rectangle,
> > well_known_colors and destination_pitch.
> > 
> > Fixes: 15bda1f8de5d ("drm/tests: Add calls to drm_fb_blit() on supported format conversion tests")
> > Signed-off-by: José Expósito <jose.exposito89@gmail.com>
> 
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>

Just a friendly reminder about this patches. Can I merge them?
They have been in the ML for a while and it doesn't look like
there are concerns.

Best wishes,
Jose
 
> > ---
> >   drivers/gpu/drm/tests/drm_format_helper_test.c | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/gpu/drm/tests/drm_format_helper_test.c b/drivers/gpu/drm/tests/drm_format_helper_test.c
> > index 86829e1cb7f0..981dada8f3a8 100644
> > --- a/drivers/gpu/drm/tests/drm_format_helper_test.c
> > +++ b/drivers/gpu/drm/tests/drm_format_helper_test.c
> > @@ -1040,6 +1040,7 @@ static void drm_test_fb_xrgb8888_to_xrgb2101010(struct kunit *test)
> >   	memset(buf, 0, dst_size);
> >   	drm_fb_xrgb8888_to_xrgb2101010(&dst, dst_pitch, &src, &fb, &params->clip, &fmtcnv_state);
> > +	buf = le32buf_to_cpu(test, (__force const __le32 *)buf, dst_size / sizeof(u32));
> >   	KUNIT_EXPECT_MEMEQ(test, buf, result->expected, dst_size);
> >   }
> 
> -- 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Frankenstrasse 146, 90461 Nuernberg, Germany
> GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
> HRB 36809 (AG Nuernberg)
> 

  reply	other threads:[~2025-08-11 10:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  9:00 [PATCH 1/2] drm/tests: Fix endian warning José Expósito
2025-06-30  9:00 ` [PATCH 2/2] drm/tests: Fix drm_test_fb_xrgb8888_to_xrgb2101010() on big-endian José Expósito
2025-06-30 11:37   ` Thomas Zimmermann
2025-08-11 10:24     ` José Expósito [this message]
2025-08-11 15:28       ` Thomas Zimmermann
2025-06-30 11:37 ` [PATCH 1/2] drm/tests: Fix endian warning Thomas Zimmermann
2025-07-01  8:22 ` Michel Dänzer
2025-07-01 16:45   ` José Expósito
2025-07-01 17:19     ` Michel Dänzer
2025-07-02  8:12     ` Thomas Zimmermann

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=aJnE6Uu_WutFA06X@fedora \
    --to=jose.exposito89@gmail.com \
    --cc=airlied@gmail.com \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gcarlos@disroot.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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

all inboxes | Powered by JetHome®