From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Vinod Koul <vkoul@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Arnd Bergmann <arnd@arndb•de>
Subject: linux-next: build warning after merge of the slave-dma tree
Date: Mon, 12 Aug 2019 17:14:11 +1000 [thread overview]
Message-ID: <20190812171411.31ec6ae3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi all,
After merging the slave-dma tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: "omap_dma_filter_fn" [vmlinux] is a static EXPORT_SYMBOL_GPL
WARNING: "edma_filter_fn" [vmlinux] is a static EXPORT_SYMBOL
Introduced by commits
9c71b9eb3cb2 ("dmaengine: omap-dma: make omap_dma_filter_fn private")
d2bfe7b5d182 ("dmaengine: edma: make edma_filter_fn private")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-12 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 7:14 Stephen Rothwell [this message]
2019-08-12 9:14 ` linux-next: build warning after merge of the slave-dma tree Arnd Bergmann
2019-08-12 9:21 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 0:00 Stephen Rothwell
2020-02-14 4:41 ` Vinod Koul
2018-11-26 5:59 Stephen Rothwell
2018-11-26 8:09 ` Vinod Koul
2018-09-13 2:22 Stephen Rothwell
2018-09-13 7:17 ` Angelo Dureghello
2018-07-04 3:30 Stephen Rothwell
2018-07-04 4:20 ` Vinod
2018-07-05 2:47 ` Stephen Rothwell
2018-07-05 5:01 ` Vinod
2016-06-09 1:18 Stephen Rothwell
2016-06-09 6:04 ` Appana Durga Kedareswara Rao
2015-03-30 6:20 Stephen Rothwell
2015-03-30 6:26 ` Appana Durga Kedareswara Rao
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=20190812171411.31ec6ae3@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=vkoul@kernel$(echo .)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