From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the drm-tegra tree
Date: Wed, 31 Mar 2021 14:42:10 +1100 [thread overview]
Message-ID: <20210331144210.7d97cc49@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
Hi all,
After merging the drm-tegra tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/gpu/drm/tegra/dc.c: In function 'tegra_cursor_atomic_update':
drivers/gpu/drm/tegra/dc.c:883:6: warning: unused variable 'dma_mask' [-Wunused-variable]
883 | u64 dma_mask = *dc->dev->dma_mask;
| ^~~~~~~~
Introduced by commit
647779e7270a ("drm/tegra: dc: Implement hardware cursor on Tegra186 and later")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-03-31 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 3:42 Stephen Rothwell [this message]
2021-03-31 8:31 linux-next: build warning after merge of the drm-tegra tree Stephen Rothwell
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=20210331144210.7d97cc49@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.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.