[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YEDkmj6cchMPAq2h@kroah.com>
Date: Thu, 4 Mar 2021 14:46:02 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Jing Xiangfeng <jingxiangfeng@...wei.com>
Cc: catalin.marinas@....com, will@...nel.org,
akpm@...ux-foundation.org, nsaenzjulienne@...e.de,
paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, rppt@...nel.org, lorenzo.pieralisi@....com,
guohanjun@...wei.com, sudeep.holla@....com, rjw@...ysocki.net,
lenb@...nel.org, song.bao.hua@...ilicon.com, ardb@...nel.org,
anshuman.khandual@....com, bhelgaas@...gle.com, guro@...com,
robh+dt@...nel.org, stable@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, frowand.list@...il.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-riscv@...ts.infradead.org,
wangkefeng.wang@...wei.com
Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA
On Wed, Mar 03, 2021 at 03:33:12PM +0800, Jing Xiangfeng wrote:
> Using two distinct DMA zones turned out to be problematic. Here's an
> attempt go back to a saner default.
What problem does this solve? How does this fit into the stable kernel
rules?
thanks,
greg k-h
Powered by blists - more mailing lists