From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: 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 dma-mapping tree
Date: Thu, 19 Aug 2021 08:54:40 +1000 [thread overview]
Message-ID: <20210819085440.0ef51c24@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hi all,
After merging the dma-mapping tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
kernel/dma/coherent.c:325:29: warning: 'dma_reserved_default_memory' defined but not used [-Wunused-variable]
325 | static struct reserved_mem *dma_reserved_default_memory __initdata;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
b7987aff1d0c ("dma-mapping: make the global coherent pool conditional")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-08-18 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 22:54 Stephen Rothwell [this message]
2021-08-19 7:02 ` 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-13 7:11 Stephen Rothwell
2021-09-03 6:45 ` Stephen Rothwell
2021-09-06 12:41 ` Christoph Hellwig
2020-09-02 0:03 Stephen Rothwell
2020-09-02 15:25 ` 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=20210819085440.0ef51c24@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--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