From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bumyong Lee <bumyong.lee@samsung.com>,
Chanho Park <chanho61.park@samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the swiotlb tree
Date: Wed, 16 Jun 2021 11:38:35 +1000 [thread overview]
Message-ID: <20210616113835.0f0d4952@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
Hi all,
After merging the swiotlb tree, today's linux-next build (powerpc
ppc64_defconfig and x86_64 allmodconfig) produced this warning:
In file included from arch/powerpc/include/asm/bug.h:109,
from include/linux/bug.h:5,
from arch/powerpc/include/asm/mmu.h:147,
from arch/powerpc/include/asm/lppaca.h:46,
from arch/powerpc/include/asm/paca.h:17,
from arch/powerpc/include/asm/current.h:13,
from include/linux/sched.h:12,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from include/linux/dma-mapping.h:7,
from include/linux/dma-direct.h:9,
from kernel/dma/swiotlb.c:24:
kernel/dma/swiotlb.c: In function 'swiotlb_bounce':
include/linux/dev_printk.h:242:23: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=]
242 | WARN_ONCE(condition, "%s %s: " format, \
| ^~~~~~~~~
include/asm-generic/bug.h:97:17: note: in definition of macro '__WARN_printf'
97 | __warn_printk(arg); \
| ^~~
include/asm-generic/bug.h:161:3: note: in expansion of macro 'WARN'
161 | WARN(1, format); \
| ^~~~
include/linux/dev_printk.h:242:2: note: in expansion of macro 'WARN_ONCE'
242 | WARN_ONCE(condition, "%s %s: " format, \
| ^~~~~~~~~
kernel/dma/swiotlb.c:355:3: note: in expansion of macro 'dev_WARN_ONCE'
355 | dev_WARN_ONCE(dev, 1,
| ^~~~~~~~~~~~~
Introduced by commit
17eb5dcf1f15 ("swiotlb: manipulate orig_addr when tlb_addr has offset")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-16 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 1:38 Stephen Rothwell [this message]
2021-06-16 2:43 ` linux-next: build warning after merge of the swiotlb tree Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2020-12-11 2:02 Stephen Rothwell
2020-12-11 2:47 ` Ashish Kalra
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=20210616113835.0f0d4952@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bumyong.lee@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=konrad.wilk@oracle.com \
--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).