From: Thomas Zimmermann <tzimmermann@suse.de>
To: alexander.stein@ew.tq-group.com, javierm@redhat.com,
airlied@gmail.com, daniel@ffwll.ch
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH v3 0/2] drm/ofdrm: Fix sparse warnings
Date: Thu, 3 Nov 2022 11:16:25 +0100 [thread overview]
Message-ID: <20221103101627.32502-1-tzimmermann@suse.de> (raw)
Fix two types of sparse warnings in ofdrm. Reported by the LKP bot.
v3:
* use IOMEM_ERR_PTR() (Javier)
v2:
* convert PCI ID endianness (Alex)
Thomas Zimmermann (2):
drm/ofdrm: Convert PCI IDs to CPU endianness for comparing
drm/ofdrm: Cast error pointers to void __iomem *
drivers/gpu/drm/tiny/ofdrm.c | 27 ++++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)
base-commit: f5a9fb2d688dfc6efa1fd779a2d225048bfb10f9
--
2.38.0
next reply other threads:[~2022-11-03 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 10:16 Thomas Zimmermann [this message]
2022-11-03 10:16 ` [PATCH v3 1/2] drm/ofdrm: Convert PCI IDs to CPU endianness for comparing Thomas Zimmermann
2022-11-03 10:16 ` [PATCH v3 2/2] drm/ofdrm: Cast error pointers to void __iomem * 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=20221103101627.32502-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@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