From: Peter Zijlstra <peterz@infradead.org>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: linux-kernel@vger.kernel.org, "x86@kernel.org" <x86@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Nilay Vaish <nilayvaish@gmail.com>, Borislav Petkov <bp@suse.de>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>, Paul Turner <pjt@google.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf/core: remove invalid warning from list_update_cgroup_event
Date: Mon, 5 Dec 2016 09:57:19 +0100 [thread overview]
Message-ID: <20161205085719.GS3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1480841177-27299-1-git-send-email-davidcc@google.com>
On Sun, Dec 04, 2016 at 12:46:17AM -0800, David Carrillo-Cisneros wrote:
> The warning introduced in commit:
>
> 979bfef8607c ("perf/core: Do not set cpuctx->cgrp for unscheduled cgroups")
That commit doesn't exist.
You instead mean this one, right?
864c2357ca89 ("perf/core: Do not set cpuctx->cgrp for unscheduled cgroups")
next prev parent reply other threads:[~2016-12-05 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 8:46 [PATCH] perf/core: remove invalid warning from list_update_cgroup_event David Carrillo-Cisneros
2016-12-05 8:57 ` Peter Zijlstra [this message]
2016-12-05 9:42 ` David Carrillo-Cisneros
2016-12-06 10:12 ` [tip:perf/urgent] perf/core: Remove invalid warning from list_update_cgroup_even()t tip-bot for David Carrillo-Cisneros
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=20161205085719.GS3092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=nilayvaish@gmail.com \
--cc=pjt@google.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@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 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.