From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: Jordan Crouse <jcrouse@codeaurora.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the drm-msm tree
Date: Mon, 21 Sep 2020 13:16:24 +1000 [thread overview]
Message-ID: <20200921131624.5e88d031@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hi all,
After merging the drm-msm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/linux/bitops.h:5,
from include/linux/kernel.h:12,
from include/linux/ascii85.h:11,
from drivers/gpu/drm/msm/adreno/adreno_gpu.c:9:
drivers/gpu/drm/msm/adreno/adreno_gpu.c: In function 'adreno_iommu_create_address_space':
include/linux/bits.h:36:11: warning: right shift count is negative [-Wshift-count-negative]
36 | (~UL(0) >> (BITS_PER_LONG - 1 - (h))))
| ^~
include/linux/bits.h:38:31: note: in expansion of macro '__GENMASK'
38 | (GENMASK_INPUT_CHECK(h, l) + __GENMASK(h, l))
| ^~~~~~~~~
drivers/gpu/drm/msm/adreno/adreno_gpu.c:212:11: note: in expansion of macro 'GENMASK'
212 | start & GENMASK(48, 0), size);
| ^~~~~~~
Introduced by commit
e3c64c7221f6 ("drm/msm: Set the global virtual address range from the IOMMU domain")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-09-21 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 3:16 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-14 2:10 linux-next: build warning after merge of the drm-msm tree Stephen Rothwell
2020-09-17 7:58 ` Stephen Rothwell
2017-11-01 3:46 Stephen Rothwell
2017-11-01 15:19 ` Rob Clark
2017-08-03 3:12 Stephen Rothwell
2017-08-03 3:09 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=20200921131624.5e88d031@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jcrouse@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
/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).