From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Jim Quinlan <james.quinlan@broadcom•com>
Subject: linux-next: build warning after merge of the dma-mapping tree
Date: Wed, 2 Sep 2020 10:03:17 +1000 [thread overview]
Message-ID: <20200902100317.142db5be@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-09-02 0:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 0:03 Stephen Rothwell [this message]
2020-09-02 15:25 ` linux-next: build warning after merge of the dma-mapping tree Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 11:48 Stephen Rothwell
2022-07-27 18:32 ` Logan Gunthorpe
2022-07-28 2:23 ` Akira Yokosawa
2022-07-28 8:57 ` Bagas Sanjaya
2021-08-18 22:54 Stephen Rothwell
2021-08-19 7:02 ` Christoph Hellwig
2021-08-13 7:11 Stephen Rothwell
2021-09-03 6:45 ` Stephen Rothwell
2021-09-06 12:41 ` Christoph Hellwig
2018-10-01 22:35 Stephen Rothwell
2018-10-02 14:22 ` Christoph Hellwig
2017-09-03 22:34 Stephen Rothwell
2017-09-04 5:51 ` Christoph Hellwig
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=20200902100317.142db5be@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--cc=james.quinlan@broadcom$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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