From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path
Date: Tue, 27 Jun 2017 14:05:55 +0200 [thread overview]
Message-ID: <20170627120555.dwcrd52dfstookmh@linutronix.de> (raw)
In-Reply-To: <20170517160530.GB18716@e104818-lin.cambridge.arm.com>
On 2017-05-17 17:05:31 [+0100], Catalin Marinas wrote:
> > Catalin, can you take this as a fix for v4.12?
>
> I queued it for 4.12-rc2. Thanks.
I backported a few patches into v4.11-RT and the backtrace popped up
(which is fixed by this patch). The problem existed before it has been
made visible. Do you intend to push this patch stable?
Sebastian
next prev parent reply other threads:[~2017-06-27 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:18 [PATCHv5] arm64/cpufeature: don't use mutex in bringup path Mark Rutland
2017-05-17 16:05 ` Catalin Marinas
2017-06-27 12:05 ` Sebastian Andrzej Siewior [this message]
2017-06-29 14:10 ` Mark Rutland
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=20170627120555.dwcrd52dfstookmh@linutronix.de \
--to=bigeasy@linutronix.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 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).