From: Liu Ying <victor.liu@nxp.com>
To: linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: tzimmermann@suse.de, airlied@linux.ie, s.hauer@pengutronix.de,
marcel.ziswiler@toradex.com, robh+dt@kernel.org,
linux-imx@nxp.com, kernel@pengutronix.de,
laurentiu.palcu@oss.nxp.com, guido.gunther@puri.sm,
shawnguo@kernel.org
Subject: [PATCH v9 4/6] drm/atomic: Avoid unused-but-set-variable warning on for_each_old_plane_in_state
Date: Mon, 29 Mar 2021 13:57:24 +0800 [thread overview]
Message-ID: <1616997446-8783-5-git-send-email-victor.liu@nxp.com> (raw)
In-Reply-To: <1616997446-8783-1-git-send-email-victor.liu@nxp.com>
Artificially use 'plane' and 'old_plane_state' to avoid 'not used' warning.
The precedent has already been set by other macros in the same file.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Liu Ying <victor.liu@nxp.com>
---
v8->v9:
* No change.
v7->v8:
* No change.
v6->v7:
* No change.
v5->v6:
* Fix commit message typo - s/Artifically/Artificially/
v4->v5:
* No change.
v3->v4:
* Add Daniel's A-b tag.
v2->v3:
* Add a missing blank line.
v1->v2:
* No change.
include/drm/drm_atomic.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
index ac5a28e..76d8dee 100644
--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -912,7 +912,10 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->planes[__i].ptr && \
((plane) = (__state)->planes[__i].ptr, \
- (old_plane_state) = (__state)->planes[__i].old_state, 1))
+ (void)(plane) /* Only to avoid unused-but-set-variable warning */, \
+ (old_plane_state) = (__state)->planes[__i].old_state, \
+ (void)(old_plane_state) /* Only to avoid unused-but-set-variable warning */, 1))
+
/**
* for_each_new_plane_in_state - iterate over all planes in an atomic update
* @__state: &struct drm_atomic_state pointer
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-29 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 5:57 [PATCH v9 0/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2021-03-29 5:57 ` [PATCH v9 1/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPU binding Liu Ying
2021-03-29 5:57 ` [PATCH v9 2/6] dt-bindings: display: imx: Add i.MX8qxp/qm PRG binding Liu Ying
2021-03-29 5:57 ` [PATCH v9 3/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPR channel binding Liu Ying
2021-03-29 14:24 ` Rob Herring
2021-03-29 5:57 ` Liu Ying [this message]
2021-03-29 5:57 ` [PATCH v9 5/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2021-04-21 11:12 ` Laurentiu Palcu
2021-03-29 5:57 ` [PATCH v9 6/6] MAINTAINERS: add maintainer for i.MX8qxp DPU DRM driver Liu Ying
2021-04-21 11:15 ` Laurentiu Palcu
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=1616997446-8783-5-git-send-email-victor.liu@nxp.com \
--to=victor.liu@nxp.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guido.gunther@puri.sm \
--cc=kernel@pengutronix.de \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).