From: Greg KH <gregkh@linuxfoundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Jing Xiangfeng <jingxiangfeng@huawei.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, guohanjun@huawei.com,
sudeep.holla@arm.com, song.bao.hua@hisilicon.com,
ardb@kernel.org, anshuman.khandual@arm.com,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Li Huafei <lihuafei1@huawei.com>
Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA
Date: Wed, 23 Jun 2021 09:12:32 +0200 [thread overview]
Message-ID: <YNLe4CGtOgVvTOMN@kroah.com> (raw)
In-Reply-To: <8b0a4f25-0803-9341-f3a4-277d16802295@huawei.com>
On Wed, Jun 23, 2021 at 02:59:59PM +0800, Kefeng Wang wrote:
> Hi Greg,
>
> There are two more patches about the ZONE_DMA[32] changes,
What ZONE_DMA changes?
> especially the
> second one, both them need be backported, thanks.
Backported to where?
> 791ab8b2e3db - arm64: Ignore any DMA offsets in the max_zone_phys()
> calculation
> 2687275a5843 - arm64: Force NO_BLOCK_MAPPINGS if crashkernel reservation is
> required
Have you tried these patches? Where do they need to be applied to?
confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Jing Xiangfeng <jingxiangfeng@huawei.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, guohanjun@huawei.com,
sudeep.holla@arm.com, song.bao.hua@hisilicon.com,
ardb@kernel.org, anshuman.khandual@arm.com,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Li Huafei <lihuafei1@huawei.com>
Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA
Date: Wed, 23 Jun 2021 09:12:32 +0200 [thread overview]
Message-ID: <YNLe4CGtOgVvTOMN@kroah.com> (raw)
In-Reply-To: <8b0a4f25-0803-9341-f3a4-277d16802295@huawei.com>
On Wed, Jun 23, 2021 at 02:59:59PM +0800, Kefeng Wang wrote:
> Hi Greg,
>
> There are two more patches about the ZONE_DMA[32] changes,
What ZONE_DMA changes?
> especially the
> second one, both them need be backported, thanks.
Backported to where?
> 791ab8b2e3db - arm64: Ignore any DMA offsets in the max_zone_phys()
> calculation
> 2687275a5843 - arm64: Force NO_BLOCK_MAPPINGS if crashkernel reservation is
> required
Have you tried these patches? Where do they need to be applied to?
confused,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-23 7:12 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 7:33 [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` [PATCH stable v5.10 1/7] arm64: mm: Move reserve_crashkernel() into mem_init() Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "arm64: mm: Move reserve_crashkernel() into mem_init()" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 2/7] arm64: mm: Move zone_dma_bits initialization into zone_sizes_init() Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 3/7] of/address: Introduce of_dma_get_max_cpu_address() Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "of/address: Introduce of_dma_get_max_cpu_address()" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 4/7] of: unittest: Add test for of_dma_get_max_cpu_address() Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "of: unittest: Add test for of_dma_get_max_cpu_address()" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 5/7] arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 6/7] arm64: mm: Set ZONE_DMA size based on early IORT scan Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "arm64: mm: Set ZONE_DMA size based on early IORT scan" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-03 7:33 ` [PATCH stable v5.10 7/7] mm: Remove examples from enum zone_type comment Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-03 7:33 ` Jing Xiangfeng
2021-03-07 15:25 ` Patch "mm: Remove examples from enum zone_type comment" has been added to the 5.10-stable tree gregkh
2021-03-07 15:25 ` gregkh
2021-03-07 15:25 ` gregkh
2021-03-04 13:46 ` [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA Greg KH
2021-03-04 13:46 ` Greg KH
2021-03-04 13:46 ` Greg KH
2021-03-04 14:05 ` Nicolas Saenz Julienne
2021-03-04 14:05 ` Nicolas Saenz Julienne
2021-03-04 14:05 ` Nicolas Saenz Julienne
2021-03-04 14:05 ` Nicolas Saenz Julienne
2021-03-04 14:17 ` Greg KH
2021-03-04 14:17 ` Greg KH
2021-03-04 14:17 ` Greg KH
2021-03-04 15:09 ` Nicolas Saenz Julienne
2021-03-04 15:09 ` Nicolas Saenz Julienne
2021-03-04 15:09 ` Nicolas Saenz Julienne
2021-03-04 15:09 ` Nicolas Saenz Julienne
2021-03-07 15:24 ` Greg KH
2021-03-07 15:24 ` Greg KH
2021-03-07 15:24 ` Greg KH
2021-03-08 3:20 ` Jing Xiangfeng
2021-03-08 3:20 ` Jing Xiangfeng
2021-03-08 3:20 ` Jing Xiangfeng
2021-03-08 9:58 ` Greg KH
2021-03-08 9:58 ` Greg KH
2021-03-08 9:58 ` Greg KH
2021-05-11 12:35 ` Kefeng Wang
2021-05-11 12:35 ` Kefeng Wang
2021-05-11 12:35 ` Kefeng Wang
2021-05-12 12:06 ` Greg KH
2021-05-12 12:06 ` Greg KH
2021-05-12 12:06 ` Greg KH
2021-06-23 6:59 ` Kefeng Wang
2021-06-23 6:59 ` Kefeng Wang
2021-06-23 7:12 ` Greg KH [this message]
2021-06-23 7:12 ` Greg KH
2021-06-23 7:25 ` Kefeng Wang
2021-06-23 7:25 ` Kefeng Wang
2021-06-23 7:34 ` Greg KH
2021-06-23 7:34 ` Greg KH
2021-06-23 8:01 ` Kefeng Wang
2021-06-23 8:01 ` Kefeng Wang
2021-06-25 10:19 ` Greg KH
2021-06-25 10:19 ` Greg KH
2021-06-26 1:19 ` Kefeng Wang
2021-06-26 1:19 ` Kefeng Wang
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=YNLe4CGtOgVvTOMN@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=jingxiangfeng@huawei.com \
--cc=lihuafei1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nsaenzjulienne@suse.de \
--cc=song.bao.hua@hisilicon.com \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.