stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Shannon Zhao <shannon.zhao@linaro.org>
Cc: <stable@vger.kernel.org>, Li Zefan <lizefan@huawei.com>
Subject: [request for stable inclusion] arm64: perf: fix unassigned cpu_pmu->plat_device when probing PMU PPIs
Date: Fri, 28 Aug 2015 11:05:48 +0800	[thread overview]
Message-ID: <55DFD00C.6070507@huawei.com> (raw)

Hi Greg and Shannon,

b265da5a45ce60bd3d7505cc0eaa6cfba50946a1
arm64: perf: fix unassigned cpu_pmu->plat_device when probing PMU PPIs

This looks applicable to stable-4.1, that fix "No PMU device registered"
when use "perf list hw"，which was introduced by commit d795ef9aa831("arm64:
perf: don't warn about missing interrupt-affinity property for PPIs").
It can be applyed to 4.1 cleanly. What do you think?

Thanks
Kefeng Wang


                 reply	other threads:[~2015-08-28  3:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=55DFD00C.6070507@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lizefan@huawei.com \
    --cc=shannon.zhao@linaro.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).