From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>, tglx@linutronix.de
Cc: peterz@infradead.org, rafael@kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
nicolas.pitre@linaro.org, vincent.guittot@linaro.org
Subject: Re: [PATCH V3 1/2] irq: Track the interrupt timings
Date: Mon, 22 Feb 2016 18:24:12 +0100 [thread overview]
Message-ID: <56CB443C.40103@linaro.org> (raw)
In-Reply-To: <56CB1FB3.2000007@linux.vnet.ibm.com>
On 02/22/2016 03:48 PM, Shreyas B Prabhu wrote:
[ ... ]
>> +
>> + free_timings(desc);
>> + free_masks(desc);
>> + free_percpu(desc->kstat_irqs);
>> + kfree(desc);
>> }
>
> I think this is a rebase error. If I am not wrong, instead of this you
> need to add free_timings(desc) to delayed_free_desc.
Ah, yes. Good catch.
Thanks for spotting it.
-- Daniel
--
<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
prev parent reply other threads:[~2016-02-22 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 15:43 [PATCH V3 1/2] irq: Track the interrupt timings Daniel Lezcano
2016-02-16 15:43 ` [PATCH V3 2/2] sched: idle: IRQ based next prediction for idle period Daniel Lezcano
2016-02-16 16:44 ` Nicolas Pitre
2016-02-17 23:09 ` Rafael J. Wysocki
2016-02-17 23:21 ` Rafael J. Wysocki
2016-02-18 10:25 ` Daniel Lezcano
2016-02-18 19:57 ` Rafael J. Wysocki
2016-02-19 15:01 ` Daniel Lezcano
2016-02-19 23:43 ` Rafael J. Wysocki
2016-02-23 9:49 ` Daniel Lezcano
2016-02-22 15:02 ` Shreyas B Prabhu
2016-02-22 17:29 ` Daniel Lezcano
2016-02-23 10:08 ` Shreyas B Prabhu
2016-02-23 10:06 ` Shreyas B Prabhu
2016-02-23 10:13 ` Daniel Lezcano
2016-02-16 16:45 ` [PATCH V3 1/2] irq: Track the interrupt timings Nicolas Pitre
2016-02-22 14:48 ` Shreyas B Prabhu
2016-02-22 17:24 ` Daniel Lezcano [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=56CB443C.40103@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=shreyas@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.