Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: "Michel Dänzer" <michel.daenzer@amd.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Monk Liu" <monk.liu@amd.com>
Subject: Re: linux-next: build warning after merge of the drm tree
Date: Fri, 2 Mar 2018 12:49:48 +1100
Message-ID: <20180302124948.0adff130@canb.auug.org.au> (raw)
In-Reply-To: <20180219101817.5f4fd5c2@canb.auug.org.au>

[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]

Hi all,

On Mon, 19 Feb 2018 10:18:17 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> In file included from include/linux/list.h:9:0,
>                  from include/linux/wait.h:7,
>                  from include/linux/wait_bit.h:8,
>                  from include/linux/fs.h:6,
>                  from include/linux/highmem.h:5,
>                  from drivers/gpu/drm/drm_memory.c:36:
> drivers/gpu/drm/drm_memory.c: In function 'drm_get_max_iomem':
> include/linux/kernel.h:808:16: warning: comparison of distinct pointer types lacks a cast
>   (void) (&max1 == &max2);   \
>                 ^
> include/linux/kernel.h:817:2: note: in expansion of macro '__max'
>   __max(typeof(x), typeof(y),   \
>   ^~~~~
> drivers/gpu/drm/drm_memory.c:159:15: note: in expansion of macro 'max'
>    max_iomem = max(max_iomem,  tmp->end);
>                ^~~
> 
> Introduced by commit
> 
>   82626363a217 ("drm: add func to get max iomem address v2")
> 
> tmp->end is a resource_size_t ...

I am still getting this warning ...

-- 
Cheers,
Stephen Rothwell

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply index

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 23:18 Stephen Rothwell
2018-03-02  1:49 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-01  7:19 Stephen Rothwell
2021-04-21  6:28 ` Stephen Rothwell
2021-03-17  7:42 Stephen Rothwell
2021-03-17  2:53 Stephen Rothwell
2021-01-22  0:59 Stephen Rothwell
2021-01-22  7:17 ` Daniel Vetter
2021-01-22  7:29   ` Stephen Rothwell
2021-01-22  8:40     ` Daniel Vetter
2021-02-01  1:55 ` Stephen Rothwell
2020-11-05  7:02 Stephen Rothwell
2020-11-16  0:01 ` Stephen Rothwell
2020-09-23  3:36 Stephen Rothwell
2020-09-23  6:27 ` Tomi Valkeinen
2020-10-01  9:47 ` Stephen Rothwell
2020-05-11  3:47 Stephen Rothwell
2020-05-11  4:04 ` Randy Dunlap
2019-02-01  0:53 Stephen Rothwell
2018-06-25  4:22 Stephen Rothwell
2018-06-25  4:22 ` Stephen Rothwell
2017-12-04  0:30 Stephen Rothwell
2017-12-04  0:57 ` Dave Airlie
2017-06-19  1:40 Stephen Rothwell
2017-05-19  2:10 Stephen Rothwell
2017-05-03 22:33 Stephen Rothwell
     [not found] ` <tencent_62AF37B85899E2EA593CCE3B@qq.com>
2017-05-04  1:42   ` Stephen Rothwell
2015-06-04 12:31 Stephen Rothwell
2015-05-20  6:54 Stephen Rothwell
2015-05-20 11:49 ` Sergey Senozhatsky
2015-05-20  6:31 Stephen Rothwell
2015-05-20 19:51 ` Russell King - ARM Linux
2013-06-28  3:30 Stephen Rothwell
2013-06-28  3:33 ` Dave Airlie
2013-04-19  5:50 Stephen Rothwell
2012-05-08  5:08 Stephen Rothwell
2011-11-28  2:41 Stephen Rothwell
2011-11-28  2:36 Stephen Rothwell
2011-05-12  2:14 Stephen Rothwell
2010-03-01  7:14 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=20180302124948.0adff130@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michel.daenzer@amd.com \
    --cc=monk.liu@amd.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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git