From: "José Expósito" <jose.exposito89@gmail.com>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, 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 1/2] drm/tests: Fix endian warning
Date: Tue, 1 Jul 2025 18:45:01 +0200 [thread overview]
Message-ID: <aGQQjTUrG8-p8qAC@fedora> (raw)
In-Reply-To: <6c2e44cc-c01a-4331-b139-152ccdbd0401@mailbox.org>
Hey Michel,
Thanks for looking into this.
On Tue, Jul 01, 2025 at 10:22:13AM +0200, Michel Dänzer wrote:
> On 30.06.25 11:00, José Expósito wrote:
> > When compiling with sparse enabled, this warning is thrown:
> >
> > warning: incorrect type in argument 2 (different base types)
> > expected restricted __le32 const [usertype] *buf
> > got unsigned int [usertype] *[assigned] buf
> >
> > Add a cast to fix it.
> >
> > Fixes: 453114319699 ("drm/format-helper: Add KUnit tests for drm_fb_xrgb8888_to_xrgb2101010()")
> > Signed-off-by: José Expósito <jose.exposito89@gmail.com>
> > ---
> > drivers/gpu/drm/tests/drm_format_helper_test.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/tests/drm_format_helper_test.c b/drivers/gpu/drm/tests/drm_format_helper_test.c
> > index 7299fa8971ce..86829e1cb7f0 100644
> > --- a/drivers/gpu/drm/tests/drm_format_helper_test.c
> > +++ b/drivers/gpu/drm/tests/drm_format_helper_test.c
> > @@ -1033,7 +1033,7 @@ static void drm_test_fb_xrgb8888_to_xrgb2101010(struct kunit *test)
> > NULL : &result->dst_pitch;
> >
> > drm_fb_xrgb8888_to_xrgb2101010(&dst, dst_pitch, &src, &fb, ¶ms->clip, &fmtcnv_state);
> > - buf = le32buf_to_cpu(test, buf, dst_size / sizeof(u32));
> > + buf = le32buf_to_cpu(test, (__force const __le32 *)buf, dst_size / sizeof(u32));
> > KUNIT_EXPECT_MEMEQ(test, buf, result->expected, dst_size);
> >
> > buf = dst.vaddr; /* restore original value of buf */
>
> It might be cleaner to use two separate variables instead of using "buf" as both little endian and host byte order. (Same for patch 2)
Yes, however, the same pattern is repeated 10 times in this file.
What do you think about fixing it in a follow up? I don't think it
should block fixing the KUnit tests.
Jose
>
> --
> Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
> https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2025-07-01 16:45 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
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 [this message]
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=aGQQjTUrG8-p8qAC@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=michel.daenzer@mailbox.org \
--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 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.