linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Export cache flush management symbols when !MULTI_CACHE
Date: Thu, 3 Jan 2013 23:11:32 +0000	[thread overview]
Message-ID: <20130103231132.GS2631@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1357252353-6200-1-git-send-email-panto@antoniou-consulting.com>

On Fri, Jan 04, 2013 at 12:32:33AM +0200, Pantelis Antoniou wrote:
> When compiling a kernel without CONFIG_MULTI_CACHE enabled the
> dma access functions end up not being exported. Fix it.

Actually, that's exactly how these are supposed to be: no driver should
_ever_ reference these symbols directly, they should all be done via
the DMA API, which internally uses these.  Therefore, none of these
should ever appear in a module.

      reply	other threads:[~2013-01-03 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 22:32 [PATCH] arm: Export cache flush management symbols when !MULTI_CACHE Pantelis Antoniou
2013-01-03 23:11 ` Russell King - ARM Linux [this message]

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=20130103231132.GS2631@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).