[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a657b44-2bc8-ee05-3a42-db7af354967e@infradead.org>
Date: Mon, 7 Aug 2017 11:49:28 -0700
From: Geoff Levand <geoff@...radead.org>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>,
linuxppc-dev@...ts.ozlabs.org
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Michael Ellerman <mpe@...erman.id.au>,
Paul Mackerras <paulus@...ba.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: block/ps3vram: Delete an error message for a failed memory
allocation in ps3vram_cache_init()
On 08/07/2017 11:34 AM, SF Markus Elfring wrote:
>> I didn't consider one would be triggered by the kzalloc failure.
>
> Do you reconsider any special system settings for further
> software evolution then?
Sorry, I don't quite understand your question.
I think your original patch is OK, and I would appreciate if
you added a check for failure of ps3vram_cache_init() in
ps3vram_probe(). If you decide not to add that check I'll
create a patch for it later.
If this doesn't answer your question, could you please
rephrase it?
-Geoff
Powered by blists - more mailing lists