From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: DMA: Silence declared inside parameter list warning for !CONFIG_MMU
Date: Wed, 6 Jul 2011 21:31:03 +0100 [thread overview]
Message-ID: <20110706203103.GT8286@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1309767141.3964.1.camel@phoenix>
On Mon, Jul 04, 2011 at 04:12:21PM +0800, Axel Lin wrote:
> Fix below warning, the struct dma_coherent_area takes no space if !CONFIG_MMU.
>
> CC arch/arm/mm/dma-mapping.o
> arch/arm/mm/dma-mapping.c:309: warning: 'struct dma_coherent_area' declared inside parameter list
> arch/arm/mm/dma-mapping.c:309: warning: its scope is only this definition or declaration, which is probably not what you want
> arch/arm/mm/dma-mapping.c:334: warning: 'struct dma_coherent_area' declared inside parameter list
> arch/arm/mm/dma-mapping.c:374: warning: 'struct dma_coherent_area' declared inside parameter list
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Ok, can you put this in the patch system please?
Thanks.
> ---
> arch/arm/mm/dma-mapping.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
> index 8089499..da3b33a 100644
> --- a/arch/arm/mm/dma-mapping.c
> +++ b/arch/arm/mm/dma-mapping.c
> @@ -297,6 +297,8 @@ static void dma_free_area(void *cpu_addr, size_t size, struct dma_coherent_area
> #define coherent_wc_area NULL
> #define coherent_dma_area NULL
>
> +struct dma_coherent_area { };
> +
> void dma_coherent_reserve(void)
> {
> }
> --
> 1.7.4.1
>
>
>
prev parent reply other threads:[~2011-07-06 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 8:12 [PATCH] ARM: DMA: Silence declared inside parameter list warning for !CONFIG_MMU Axel Lin
2011-07-06 20:31 ` 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=20110706203103.GT8286@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).