From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/twd: avoid waking deeply sleeping CPUs for rate change notifier
Date: Tue, 06 Nov 2018 17:29:13 +0100 [thread overview]
Message-ID: <1541521753.5822.27.camel@pengutronix.de> (raw)
In-Reply-To: <20180417104627.29643-1-l.stach@pengutronix.de>
On Tue, 2018-04-17 at 12:46 +0200, Lucas Stach wrote:
[...]
> @@ -326,6 +350,9 @@ static int __init twd_local_timer_common_register(struct device_node *np)
> {
> int err;
>
> + if (!zalloc_cpumask_var(&active_twd_mask, GFP_KERNEL))
> + return -ENOMEM;
> +
> twd_evt = alloc_percpu(struct clock_event_device);
> if (!twd_evt) {
> err = -ENOMEM;
This could free_cpumask_var(active_twd_mask) in the error path.
regards
Philipp
next prev parent reply other threads:[~2018-11-06 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:46 [PATCH] arm/twd: avoid waking deeply sleeping CPUs for rate change notifier Lucas Stach
2018-06-11 16:16 ` Lucas Stach
2018-10-29 11:34 ` Lucas Stach
2018-10-29 12:30 ` Daniel Lezcano
2018-11-06 17:25 ` Russell King - ARM Linux
2018-11-18 1:48 ` Daniel Lezcano
2018-11-06 16:29 ` Philipp Zabel [this message]
2019-12-02 16:45 Lucas Stach
2019-12-05 20:29 ` 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=1541521753.5822.27.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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 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.