public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Liu Hua <sdu.liu@huawei.com>, nicolas.pitre@linaro.org
Cc: linux@arm.linux.org.uk, will.deacon@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, wangnan0@huawei.com,
	peifeiyue@huawei.com, liusdu@126.com
Subject: Re: [PATCH v2 1/2] ARM : DMA : remove useless information about DMA
Date: Fri, 11 Apr 2014 12:39:40 +0200	[thread overview]
Message-ID: <5347C66C.2040304@samsung.com> (raw)
In-Reply-To: <1397203252-22977-2-git-send-email-sdu.liu@huawei.com>

Hello,

On 2014-04-11 10:00, Liu Hua wrote:
> Because commit e9da6e9905e6 has remove custom consistent dma
> region. So the related variable and document should be removed
>
> Signed-off-by: Liu Hua <sdu.liu@huawei.com>

Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>

> ---
>   Documentation/arm/memory.txt  | 4 ----
>   arch/arm/include/asm/memory.h | 2 --
>   2 files changed, 6 deletions(-)
>
> diff --git a/Documentation/arm/memory.txt b/Documentation/arm/memory.txt
> index 4bfb9ff..8a361c0 100644
> --- a/Documentation/arm/memory.txt
> +++ b/Documentation/arm/memory.txt
> @@ -44,10 +44,6 @@ fffe0000	fffe7fff	ITCM mapping area for platforms with
>   fff00000	fffdffff	Fixmap mapping region.  Addresses provided
>   				by fix_to_virt() will be located here.
>   
> -ffc00000	ffefffff	DMA memory mapping region.  Memory returned
> -				by the dma_alloc_xxx functions will be
> -				dynamically mapped here.
> -
>   ff000000	ffbfffff	Reserved for future expansion of DMA
>   				mapping region.
>   
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> index 02fa255..2b75146 100644
> --- a/arch/arm/include/asm/memory.h
> +++ b/arch/arm/include/asm/memory.h
> @@ -83,8 +83,6 @@
>    */
>   #define IOREMAP_MAX_ORDER	24
>   
> -#define CONSISTENT_END		(0xffe00000UL)
> -
>   #else /* CONFIG_MMU */
>   
>   /*

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


  reply	other threads:[~2014-04-11 10:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  8:00 [PATCH v2 0/2] change ARM linux memory layout to support 32 CPUs Liu Hua
2014-04-11  8:00 ` [PATCH v2 1/2] ARM : DMA : remove useless information about DMA Liu Hua
2014-04-11 10:39   ` Marek Szyprowski [this message]
2014-04-12  3:12   ` Nicolas Pitre
2014-04-12  3:31     ` Nicolas Pitre
2014-04-12  4:25     ` Liu hua
2014-04-12 14:32       ` Nicolas Pitre
2014-04-13 12:10         ` Liu hua
2014-04-13 16:42           ` Nicolas Pitre
2014-04-11  8:00 ` [PATCH v2 2/2] ARM : change fixmap mapping region to support 32 CPUs Liu Hua
2014-04-12  3:26   ` Nicolas Pitre
2014-04-13 13:25     ` Liu hua
2014-04-13 17:34       ` Nicolas Pitre
2014-04-14 12:28         ` Liu hua
2014-04-14 13:50           ` Nicolas Pitre
2014-04-15 11:04             ` Liu hua
2014-04-12  3:29 ` [PATCH v2 0/2] change ARM linux memory layout " Nicolas Pitre

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=5347C66C.2040304@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liusdu@126.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=peifeiyue@huawei.com \
    --cc=sdu.liu@huawei.com \
    --cc=wangnan0@huawei.com \
    --cc=will.deacon@arm.com \
    /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