From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: <zhe.he@windriver.com>
To: He Zhe <zhe.he@windriver.com>
To: <catalin.marinas@arm.com>, <stable@vger.kernel.org>,
Cc: stable@vger.kernel.org
Cc: catalin.marinas@arm.com
Cc: bigeasy@linutronix.de
Cc: tglx@linutronix.de
Cc: rostedt@goodmis.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] kmemleak: Turn kmemleak_lock to raw spinlock on RT
Date: Wed, 14 Nov 2018 18:09:21 +0000 [thread overview]
Message-ID: <20181114180922.1EEFD2243E@mail.kernel.org> (raw)
In-Reply-To: <1542017835-431346-1-git-send-email-zhe.he@windriver.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.1, v4.18.18, v4.14.80, v4.9.136, v4.4.163, v3.18.125.
v4.19.1: Build OK!
v4.18.18: Build OK!
v4.14.80: Build OK!
v4.9.136: Build OK!
v4.4.163: Build OK!
v3.18.125: Failed to apply! Possible dependencies:
Unable to calculate
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-14 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 10:17 [PATCH] kmemleak: Turn kmemleak_lock to raw spinlock on RT zhe.he
2018-11-14 18:09 ` Sasha Levin [this message]
2018-11-22 9:02 ` He Zhe
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=20181114180922.1EEFD2243E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.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).