From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource/drivers/timer-atmel-pit: properly handle error cases
Date: Thu, 27 Sep 2018 12:00:35 +0200 [thread overview]
Message-ID: <f5f48a3e-233d-99e8-bd8c-978b4ca2a7cc@linaro.org> (raw)
In-Reply-To: <d2b356f9-6a29-0ce2-c511-ac1aff8e91ca@microchip.com>
On 26/09/2018 14:38, Nicolas Ferre wrote:
> Daniel,
>
> On 01/05/2018 at 10:36, Daniel Lezcano wrote:
>> On Wed, Apr 25, 2018 at 12:14:39PM +0200, Alexandre Belloni wrote:
>>> smatch now reports a possible leak:
>>>
>>> smatch warnings:
>>> drivers/clocksource/timer-atmel-pit.c:183 at91sam926x_pit_dt_init()
>>> warn: possible memory leak of 'data'
>>>
>>> Ensure data is freed before exiting with an error.
>>>
>>> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
>>> ---
>>
>> Applied for 4.17-rc
>
> We don't see it in Mainline as of 4.19-rc neither in linux-next. Has it
> been forgotten?
Yes, my bad. I thought it was merge in tip:timers/urgent
Let me resend another PR for 4.19-rc and Cc stable@
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-09-27 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 10:14 [PATCH] clocksource/drivers/timer-atmel-pit: properly handle error cases Alexandre Belloni
2018-05-01 8:36 ` Daniel Lezcano
2018-09-26 12:38 ` Nicolas Ferre
2018-09-27 10:00 ` Daniel Lezcano [this message]
[not found] <ea561d6f-22f8-b1f7-a063-d559900a9004@linaro.org>
2018-09-27 14:51 ` [PATCH] clocksource/drivers/timer-atmel-pit: Properly " Daniel Lezcano
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=f5f48a3e-233d-99e8-bd8c-978b4ca2a7cc@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).