From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: linux-next: build warning after merge of the iommu tree
Date: Thu, 8 Nov 2018 12:39:38 +1100 [thread overview]
Message-ID: <20181108123938.2026559e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Hi Joerg,
After merging the iommu tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/bitmap.h:10,
from drivers/iommu/intel-iommu.c:24:
drivers/iommu/intel-iommu.c: In function 'iommu_calculate_agaw':
include/linux/kernel.h:845:29: warning: comparison of distinct pointer types lacks a cast
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^~
include/linux/kernel.h:859:4: note: in expansion of macro '__typecheck'
(__typecheck(x, y) && __no_side_effects(x, y))
^~~~~~~~~~~
include/linux/kernel.h:869:24: note: in expansion of macro '__safe_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^~~~~~~~~~
include/linux/kernel.h:878:19: note: in expansion of macro '__careful_cmp'
#define min(x, y) __careful_cmp(x, y, <)
^~~~~~~~~~~~~
drivers/iommu/intel-iommu.c:668:9: note: in expansion of macro 'min'
mgaw = min(cap_mgaw(iommu->cap), DEFAULT_DOMAIN_ADDRESS_WIDTH);
^~~
Introduced by commit
248808a0fad0 ("iommu/vt-d: Respect max guest address width in agaw")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-11-08 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 1:39 Stephen Rothwell [this message]
2018-11-08 9:30 ` linux-next: build warning after merge of the iommu tree Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2019-02-27 2:20 Stephen Rothwell
2019-02-27 18:48 ` sathyanarayanan kuppuswamy
2021-06-08 3:56 Stephen Rothwell
2024-07-09 9:06 Stephen Rothwell
2024-07-09 10:08 ` Will Deacon
2025-07-16 10:42 Stephen Rothwell
2025-07-17 10:04 ` Will Deacon
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=20181108123938.2026559e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ashok.raj@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).