[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210510185238.787adc7378bc6d82262399d2@linux-foundation.org>
Date: Mon, 10 May 2021 18:52:38 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Uladzislau Rezki <urezki@...il.com>
Cc: Matthew Wilcox <willy@...radead.org>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
Nicholas Piggin <npiggin@...il.com>,
Mel Gorman <mgorman@...e.de>, Hillf Danton <hdanton@...a.com>,
Michal Hocko <mhocko@...e.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...ymobile.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH v2 2/2] mm/vmalloc: Print a warning message first on
failure
On Mon, 10 May 2021 12:33:42 +0200 Uladzislau Rezki <urezki@...il.com> wrote:
> Please find the v4 version of the patch that is in question:
>
> >From 7e27e4ac8f299ae244e9e0e90e0292ae2c08d37d Mon Sep 17 00:00:00 2001
> From: "Uladzislau Rezki (Sony)" <urezki@...il.com>
> Date: Sat, 8 May 2021 23:41:21 +0200
> Subject: [PATCH v4 1/1] mm/vmalloc: Print a warning message first on failure
Added, thanks.
Matthew has a point of course, but I do think that any console driver
which tries to allocate memory within the cotext of printk() is so
pathetic that it isn't worth compromising core code to cater for it...
Powered by blists - more mailing lists