linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ladislav Michl <ladis@linux-mips.org>,
	SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	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
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Tue, 28 Nov 2017 06:36:50 -0800	[thread overview]
Message-ID: <1511879810.19952.16.camel@perches.com> (raw)
In-Reply-To: <20171128102327.GA30267@lenoch>

On Tue, 2017-11-28 at 11:23 +0100, Ladislav Michl wrote:
> I do not follow. This is OMAP framebuffer driver, so in this case, there
> is zero variation. Could you, please, review following patch and verify
> is it satisfies your automated static code analysis test?

Obviously a better patch.

I suggest submitting it properly and letting the 0-day
build bot have a go at it.

cheers, Joe

  parent reply	other threads:[~2017-11-28 14:36 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
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 [this message]
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=1511879810.19952.16.camel@perches.com \
    --to=joe@perches.com \
    --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=julia.lawall@lip6.fr \
    --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).