From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 0/4] random fixes
Date: Mon, 19 Nov 2018 09:10:13 +0100 [thread overview]
Message-ID: <20181119081013.lo6i7wfsafum57l6@pengutronix.de> (raw)
In-Reply-To: <20181116101032.3358-1-linux@rempel-privat.de>
On Fri, Nov 16, 2018 at 11:10:28AM +0100, Oleksij Rempel wrote:
> Some random fixes for issues found by https://app.codacy.com
>
> Oleksij Rempel (4):
> ddr_spd: remove unused array
> video/ssd1307fb: fix potential memory leak on error
> clk: imx: cpu: avoid use after free on error
> of: partition: set ret for error cases
>
> common/ddr_spd.c | 2 --
> drivers/clk/imx/clk-cpu.c | 4 +++-
> drivers/of/partition.c | 4 ++--
> drivers/video/ssd1307fb.c | 7 +++++--
> 4 files changed, 10 insertions(+), 7 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-11-19 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:10 Oleksij Rempel
2018-11-16 10:10 ` [PATCH v2 1/4] ddr_spd: remove unused array Oleksij Rempel
2018-11-16 10:10 ` [PATCH v2 2/4] video/ssd1307fb: fix potential memory leak on error Oleksij Rempel
2018-11-16 10:10 ` [PATCH v2 3/4] clk: imx: cpu: avoid use after free " Oleksij Rempel
2018-11-16 10:10 ` [PATCH v2 4/4] of: partition: set ret for error cases Oleksij Rempel
2018-11-19 8:10 ` Sascha Hauer [this message]
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=20181119081013.lo6i7wfsafum57l6@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.de \
/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