From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751899AbdK1J4t (ORCPT <rfc822;w@1wt.eu>);
        Tue, 28 Nov 2017 04:56:49 -0500
Received: from mout.web.de ([212.227.15.3]:63370 "EHLO mout.web.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750835AbdK1J4p (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 28 Nov 2017 04:56:45 -0500
Subject: Re: omapfb/dss: Delete an error message for a failed memory
 allocation in three functions
To: Julia Lawall <julia.lawall@lip6.fr>, linux-omap@vger.kernel.org,
        linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: Joe Perches <joe@perches.com>, "Andrew F. Davis" <afd@ti.com>,
        Arvind Yadav <arvind.yadav.cs@gmail.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        Tomi Valkeinen <tomi.valkeinen@ti.com>,
        LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
References: <c48a01db-c477-3bd3-5cb4-548e47810ccb@users.sourceforge.net>
 <d29a0bae-7b6f-b8f6-6809-5a097cd5a26a@ti.com>
 <1511809633.32426.70.camel@perches.com>
 <d82fbab2-865f-3051-f487-d310ee819cf3@users.sourceforge.net>
 <1511833514.32426.86.camel@perches.com>
 <7e7e64cf-dbe5-614a-f1e5-29d7b6cf9297@users.sourceforge.net>
 <alpine.DEB.2.20.1711280844180.2450@hadrien>
 <c504db1d-415a-9bd4-172c-b1c17dd3740f@users.sourceforge.net>
 <alpine.DEB.2.20.1711281025210.3443@hadrien>
From: SF Markus Elfring <elfring@users.sourceforge.net>
Message-ID: <62306606-9e30-d33d-d059-07fdcdbaae92@users.sourceforge.net>
Date: Tue, 28 Nov 2017 10:56:25 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1711281025210.3443@hadrien>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:nGPUCggCHmsrw1ouRVr1+SuQJWlyw19lg1HQsEqSV2HIIhy22Os
 Hq0KdyjSz7t0rr0jaJmqpA+x39CIa5fEOaZ+qW5Qy1x1HxftBHrlUS8I/T3HNSfBPIma/gQ
 Eu6ulodrql1joz9nyhaNn9K6JVXE5WTs5+0pQDWLcqyKr/MYpDlyfJDKn/s49PLZxgKRmlB
 xvARh4D4YKqDI4hGsqKzw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:t1m9HcPaKOQ=:tr3/PZNEzTU984CO2tuwrz
 LXC/BNhyJvPSQpwjgfWoEQXPK3b5QbasjB+Efm79T/GQIz/Hxkc+Yo3V3pD1wz6sWVmugs4gN
 lSWr/xSATC2dM5pVhHvE3BVwXD76J2sTORHv7lMKiPfnmNKd0YBHewJYV+gr5HI49CeGEvLy4
 f61HAHZ8N3N5FihomCyOao2ii+6EGyDX+hlpQazD4/kwK/H8prowadLgA+mWZmcJ7jUAy4RbH
 EM078i/em7AtW7dYa4Q0Y156NJwdEcmDoV3i5hRGYEwoFMsZ8E4372x9bttYFbh3dR1T/CUgZ
 8sUxHXkaVeSuFr9Idh97+4jvI+WClPnjw/9pF76QFODZHavNLx3ZS5mwcTrlvhVG9lxkoWiBd
 XJui92sQb7TVN8t3e2DibMWPpUb/ns+3KdRLkeK8x3gJbCxJjrgi/VCsp2HCCHiwAht+6x2G6
 xJOlEZ0zApi9IoJd9nIwXfz1Gt93tw7A1M15/nPtRVc5RBE9fo7SHTj2mv7Wq+05EE2dgnec8
 886mSsUWbLt/Q25SAugIT+OGHChJ6tpishVidE18Ba3i7O/1jC0PuXXR6isbT/eGdY5yyFouW
 d8TGEuhPxXO0w2L0aNufrMr5jEsZhS8M8CGs02I+vEi6zxwuHJrCYkpdGAbodw7PA1syAaaZW
 uGlU9ERCs9FPwZ/o/0+TjsD9lGSjkD3BRT2R8U4hA2wAzCSWVxSRXHw+DiKML5qXyabx4IWIX
 ENvkY6Qy16ZxQUaHm0jx/AA373med9rNPGLXrqsNNTbh8QGjas4+gFAtN14AeVUmnYwU4QFyj
 WP0WxGMKKo1Po1woZKef4vakVgvqgZTUdmDEOG4UZ5JiYHgMcw=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

>> I got an other impression. The probability for disagreements is increasing
>> in relation to the number of contributors to which I show change possibilities.
> 
> No.  You should learn from the previous submissions what concerns people
> have and address them up front.

The concerns can vary as contributors and changes are different.

How would you like to “address” the data structure for a default allocation
failure report finally?

Regards,
Markus