From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bartlomiej Zolnierkiewicz Subject: Re: [PATCH 3/3] video: fbdev: don't print error message on framebuffer_alloc() failure Date: Fri, 28 Jun 2019 12:27:51 +0200 Message-ID: <4a534d3e-0ce6-9dfd-b3f2-e69aa0a1fcd8@samsung.com> References: <3da197ed-a701-2aa7-d775-2bdbe9deab4a@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <3da197ed-a701-2aa7-d775-2bdbe9deab4a@samsung.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org Cc: =?UTF-8?Q?Bruno_Pr=c3=a9mont?= , Jiri Kosina , Benjamin Tissoires List-Id: linux-input@vger.kernel.org On 6/14/19 4:51 PM, Bartlomiej Zolnierkiewicz wrote: > framebuffer_alloc() can fail only on kzalloc() memory allocation > failure and since kzalloc() will print error message in such case > we can omit printing extra error message in drivers (which BTW is > what the majority of framebuffer_alloc() users is doing already). > > Cc: "Bruno Prémont" > Cc: Jiri Kosina > Cc: Benjamin Tissoires > Signed-off-by: Bartlomiej Zolnierkiewicz I queued the patch for v5.3. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics