From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Tue, 08 Aug 2017 08:23:50 +0000 Subject: Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init() Message-Id: List-Id: References: <8d140d00-935c-da0a-ff2e-167abe642bda@infradead.org> <32cdcd8a-1000-223c-71da-4c9119954d4e@users.sourceforge.net> <3a657b44-2bc8-ee05-3a42-db7af354967e@infradead.org> <57b472a0-0245-f821-cea8-171c34cc9df7@users.sourceforge.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Geoff Levand , linuxppc-dev@lists.ozlabs.org Cc: LKML , kernel-janitors@vger.kernel.org, Benjamin Herrenschmidt , Jens Axboe , Jim Paris , Michael Ellerman , Paul Mackerras >> https://patchwork.ozlabs.org/patch/798575/ > > I submitted your patch Thanks for your constructive feedback. https://patchwork.ozlabs.org/patch/798850/ > and a fix to ps3vram_probe() with the other patches in my queue. I find it nice that you picked this change opportunity up after a bit of discussion (before an other developer would eventually have tackled it also). “Check return of ps3vram_cache_init” https://patchwork.ozlabs.org/patch/798853/ 1. Unfortunately, I find that this specific update suggestion does not fit to the Linux coding style convention. “… Do not unnecessarily use braces where a single statement will do. …” 2. How do you think about to use the check “if (error)” instead? 3. Will an additional commit description be useful? Regards, Markus