All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@marvell.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@kernel.org>,
	linux@arm.linux.org.uk, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle()
Date: Thu, 24 Sep 2015 11:18:54 +0800	[thread overview]
Message-ID: <20150924111854.43429ca2@xhacker> (raw)
In-Reply-To: <20150923180814.GL23801@atomide.com>

Dear Tony,

On Wed, 23 Sep 2015 11:08:15 -0700
Tony Lindgren <tony@atomide.com> wrote:

> * Kevin Hilman <khilman@kernel.org> [150923 11:03]:
> > Jisheng Zhang <jszhang@marvell.com> writes:
> > 
> > > The cpuidle tracepoints are called within a rcu_idle_exit() section, and
> > > must be denoted with the _rcuidle() version of the tracepoint.
> > >
> > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >  
> > Acked-by: Kevin Hilman <khilman@linaro.org>
> 
> Hmm is this needed as a fix for the -rc cycle or can this wait
> for v4.4?

IMHO, this is a fix. But it can wait for v4.4 merge window.

Thanks,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle()
Date: Thu, 24 Sep 2015 11:18:54 +0800	[thread overview]
Message-ID: <20150924111854.43429ca2@xhacker> (raw)
In-Reply-To: <20150923180814.GL23801@atomide.com>

Dear Tony,

On Wed, 23 Sep 2015 11:08:15 -0700
Tony Lindgren <tony@atomide.com> wrote:

> * Kevin Hilman <khilman@kernel.org> [150923 11:03]:
> > Jisheng Zhang <jszhang@marvell.com> writes:
> > 
> > > The cpuidle tracepoints are called within a rcu_idle_exit() section, and
> > > must be denoted with the _rcuidle() version of the tracepoint.
> > >
> > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >  
> > Acked-by: Kevin Hilman <khilman@linaro.org>
> 
> Hmm is this needed as a fix for the -rc cycle or can this wait
> for v4.4?

IMHO, this is a fix. But it can wait for v4.4 merge window.

Thanks,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@kernel.org>, <linux@arm.linux.org.uk>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle()
Date: Thu, 24 Sep 2015 11:18:54 +0800	[thread overview]
Message-ID: <20150924111854.43429ca2@xhacker> (raw)
In-Reply-To: <20150923180814.GL23801@atomide.com>

Dear Tony,

On Wed, 23 Sep 2015 11:08:15 -0700
Tony Lindgren <tony@atomide.com> wrote:

> * Kevin Hilman <khilman@kernel.org> [150923 11:03]:
> > Jisheng Zhang <jszhang@marvell.com> writes:
> > 
> > > The cpuidle tracepoints are called within a rcu_idle_exit() section, and
> > > must be denoted with the _rcuidle() version of the tracepoint.
> > >
> > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >  
> > Acked-by: Kevin Hilman <khilman@linaro.org>
> 
> Hmm is this needed as a fix for the -rc cycle or can this wait
> for v4.4?

IMHO, this is a fix. But it can wait for v4.4 merge window.

Thanks,
Jisheng


  reply	other threads:[~2015-09-24  3:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  5:41 [PATCH] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle() Jisheng Zhang
2015-09-18  5:41 ` Jisheng Zhang
2015-09-18  5:41 ` Jisheng Zhang
2015-09-23 17:59 ` Kevin Hilman
2015-09-23 17:59   ` Kevin Hilman
2015-09-23 17:59   ` Kevin Hilman
2015-09-23 18:08   ` Tony Lindgren
2015-09-23 18:08     ` Tony Lindgren
2015-09-24  3:18     ` Jisheng Zhang [this message]
2015-09-24  3:18       ` Jisheng Zhang
2015-09-24  3:18       ` Jisheng Zhang
2015-10-12 23:10       ` Tony Lindgren
2015-10-12 23:10         ` Tony Lindgren

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=20150924111854.43429ca2@xhacker \
    --to=jszhang@marvell.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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.