linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Ladislav Michl <ladis@linux-mips.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	"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"
	<kernel-janitors@vger.kernel.org>
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Mon, 27 Nov 2017 19:56:12 +0100	[thread overview]
Message-ID: <CAMuHMdWqrTw80_t8Jr_ejzcLevXdxr-gnYgOQhk1-Mhn+v=A=w@mail.gmail.com> (raw)
In-Reply-To: <5e90409f-fcb0-cdb6-9bc3-26ad30a1f7c9@users.sourceforge.net>

Hi Markus,

On Mon, Nov 27, 2017 at 7:12 PM, SF Markus Elfring
<elfring@users.sourceforge.net> wrote:
>>> Can a default allocation failure report provide the information
>>> which you might expect so far?
>>
>> You should be able to answer that question yourself.
>
> I can not answer this detail completely myself because my knowledge
> is incomplete about your concrete expectations for the exception handling
> which can lead to different views for the need of additional error messages.

It may be a good idea to try to trigger an out-of-memory condition yourself,
and see what happens?

>> And if you are unable to do so, just do not sent changes pointed
>> by any code analysis tools.
>
> They can point aspects out for further software development considerations,
> can't they?

Sure. But I think it is a good experience to witness what can happen if you
"violate" these "coding standards written by other people", and learn to
understand why they were written, increasing your own knowledge.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2017-11-27 18:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 18:55 [PATCH] omapfb/dss: Delete an error message for a failed memory allocation in three functions SF Markus Elfring
2017-11-27 16:43 ` Andrew F. Davis
2017-11-27 17:27   ` SF Markus Elfring
2017-11-27 17:44     ` Ladislav Michl
2017-11-27 18:12       ` SF Markus Elfring
2017-11-27 18:56         ` Geert Uytterhoeven [this message]
2017-11-27 19:22         ` Ladislav Michl
2017-11-27 22:20           ` Ladislav Michl
2017-11-27 19:07   ` [PATCH] " Joe Perches
2017-11-27 21:33     ` Andrew F. Davis
2017-11-27 21:45       ` Ladislav Michl
2017-11-27 21:48     ` SF Markus Elfring
2017-11-28  1:45       ` Joe Perches
2017-11-28  7:41         ` SF Markus Elfring
2017-11-28  7:49           ` Julia Lawall
2017-11-28  8:49             ` SF Markus Elfring
2017-11-28  9:26               ` Julia Lawall
2017-11-28  9:56                 ` SF Markus Elfring
2017-11-28  8:04           ` Joe Perches
2017-11-28  8:49             ` Ladislav Michl
2017-11-28  9:11             ` SF Markus Elfring
2017-11-28  9:28               ` Julia Lawall
2017-11-28 10:15                 ` SF Markus Elfring
2017-11-28 10:23                   ` Ladislav Michl
2017-11-28 10:50                     ` SF Markus Elfring
2017-11-28 11:41                       ` Ladislav Michl
2017-11-28 12:13                         ` SF Markus Elfring
2017-11-28 17:50                           ` Ladislav Michl
2017-11-28 18:09                             ` SF Markus Elfring
2017-11-28 14:36                     ` Joe Perches
2017-12-03 18:20             ` SF Markus Elfring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMuHMdWqrTw80_t8Jr_ejzcLevXdxr-gnYgOQhk1-Mhn+v=A=w@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=afd@ti.com \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=ladis@linux-mips.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).