Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vinod Koul <vkoul@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the slave-dma tree
Date: Mon, 12 Aug 2019 11:14:08 +0200
Message-ID: <CAK8P3a0eOyD2iTFeLC1J95WMAwyzBJJ0S5nOb+Z_y9nUy=8=qg@mail.gmail.com> (raw)
In-Reply-To: <20190812171411.31ec6ae3@canb.auug.org.au>

On Mon, Aug 12, 2019 at 9:14 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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")

The warning is valid, I will send a fix.

I have never seen this message though, I guess the build system just introduced
a check for this? I don't see where this would come from in next-20190809
(only checking with grep, not actually trying to build right now).

      Arnd

  reply index

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12  7:14 Stephen Rothwell
2019-08-12  9:14 ` Arnd Bergmann [this message]
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='CAK8P3a0eOyD2iTFeLC1J95WMAwyzBJJ0S5nOb+Z_y9nUy=8=qg@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vkoul@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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git