From: Sasha Levin <sasha.levin@oracle.com>
To: He Kuang <hekuang@huawei.com>
Cc: stable@vger.kernel.org, wangnan0@huawei.com
Subject: Re: [PATCH 0/5] upstream patches to 4.1 stable
Date: Thu, 24 Mar 2016 11:14:14 -0400 [thread overview]
Message-ID: <56F40446.60901@oracle.com> (raw)
In-Reply-To: <1458818093-7419-1-git-send-email-hekuang@huawei.com>
On 03/24/2016 07:14 AM, He Kuang wrote:
> Here are some patches from master branch related to perf subsystem.
>
> Alexander Shishkin (1):
> perf/core: Fix perf_sched_count derailment
>
> Peter Zijlstra (2):
> perf: Do not double free
> perf: Cure event->pending_disable race
>
> Yang Shi (2):
> arm64: replace read_lock to rcu lock in call_break_hook
> arm64: replace read_lock to rcu lock in call_step_hook
>
> arch/arm64/kernel/debug-monitors.c | 42 ++++++++++++++++++++------------------
> kernel/events/core.c | 20 ++++++++++--------
> 2 files changed, 34 insertions(+), 28 deletions(-)
>
Grabbed it. Thanks!
Thanks,
Sasha
prev parent reply other threads:[~2016-03-24 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 11:14 [PATCH 0/5] upstream patches to 4.1 stable He Kuang
2016-03-24 11:14 ` [PATCH 1/5] arm64: replace read_lock to rcu lock in call_break_hook He Kuang
2016-03-24 11:14 ` [PATCH 2/5] arm64: replace read_lock to rcu lock in call_step_hook He Kuang
2016-03-24 11:14 ` [PATCH 3/5] perf: Do not double free He Kuang
2016-03-24 11:14 ` [PATCH 4/5] perf: Cure event->pending_disable race He Kuang
2016-03-24 11:14 ` [PATCH 5/5] perf/core: Fix perf_sched_count derailment He Kuang
2016-03-24 14:15 ` [PATCH 0/5] upstream patches to 4.1 stable Greg KH
2016-03-25 7:33 ` Hekuang
2016-03-24 15:14 ` Sasha Levin [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=56F40446.60901@oracle.com \
--to=sasha.levin@oracle.com \
--cc=hekuang@huawei.com \
--cc=stable@vger.kernel.org \
--cc=wangnan0@huawei.com \
/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).