[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200817183636.GG3464@kozik-lap>
Date: Mon, 17 Aug 2020 20:36:36 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Russell King <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Markus Mayer <mmayer@...adcom.com>,
Roger Quadros <rogerq@...com>,
Tony Lindgren <tony@...mide.com>,
Vladimir Zapolskiy <vz@...ia.com>,
Kukjin Kim <kgene@...nel.org>,
Lukasz Luba <lukasz.luba@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
linux-pm@...r.kernel.org
Cc: Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [RFT 08/16] memory: omap-gpmc: Use WARN() instead of BUG() on
wrong free
On Fri, Jul 24, 2020 at 08:23:20PM +0200, Krzysztof Kozlowski wrote:
> Since driver tracks reserved memory, freeing a non-reserved GPMC should
> not be fatal and crash the system. Printing a warning is friendlier.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org>
>
> ---
>
> Not tested on HW.
> ---
> drivers/memory/omap-gpmc.c | 3 +--
Applied.
Best regards,
Krzysztof
Powered by blists - more mailing lists