All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hekuang <hekuang@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <sasha.levin@oracle.com>, <stable@vger.kernel.org>,
	<wangnan0@huawei.com>
Subject: Re: [PATCH 0/5] upstream patches to 4.1 stable
Date: Fri, 25 Mar 2016 15:33:54 +0800	[thread overview]
Message-ID: <56F4E9E2.7050005@huawei.com> (raw)
In-Reply-To: <20160324141527.GB22215@kroah.com>

hi,

在 2016/3/24 22:15, Greg KH 写道:
> On Thu, Mar 24, 2016 at 11:14:48AM +0000, He Kuang wrote:
>> Here are some patches from master branch related to perf subsystem.
> Why only 4.1?  What about 4.4?

Our product is based on 4.1 kernel, I'll pick some important patches 
related to perf subsystem
from master branch and cherry-pick them to 4.1 stable, then verify that 
they are able to work
properly,  4.4 is beyond my work scope.

Thanks.

>
> thanks,
>
> greg k-h
>



  reply	other threads:[~2016-03-25  7:37 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 [this message]
2016-03-24 15:14 ` Sasha Levin

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=56F4E9E2.7050005@huawei.com \
    --to=hekuang@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=sasha.levin@oracle.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 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.