linux-kernel - linux-next: build warning after merge of the dma-mapping tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200902100317.142db5be@canb.auug.org.au>
Date:   Wed, 2 Sep 2020 10:03:17 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Christoph Hellwig <hch@....de>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jim Quinlan <james.quinlan@...adcom.com>
Subject: linux-next: build warning after merge of the dma-mapping tree

Hi all,

After merging the dma-mapping tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

In file included from arch/arm/mach-keystone/keystone.c:24:
arch/arm/mach-keystone/keystone.c: In function 'keystone_platform_notifier':
arch/arm/mach-keystone/memory.h:17:34: warning: conversion from 'long long unsigned int' to 'phys_addr_t' {aka 'unsigned int'} changes value from '34359738368' to '0' [-Woverflow]
   17 | #define KEYSTONE_HIGH_PHYS_START 0x800000000ULL
      |                                  ^~~~~~~~~~~~~~
arch/arm/mach-keystone/keystone.c:40:39: note: in expansion of macro 'KEYSTONE_HIGH_PHYS_START'
   40 |   int ret = dma_set_offset_range(dev, KEYSTONE_HIGH_PHYS_START,
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~

Introduced by commit

  eef520b232c6 ("dma-mapping: introduce DMA range map, supplanting dma_pfn_offset")

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped