From: David Brown <davidb@codeaurora.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] msm: timer: Support sched_clock()
Date: Fri, 24 Feb 2012 17:10:00 -0800 [thread overview]
Message-ID: <20120225011000.GA4611@codeaurora.org> (raw)
In-Reply-To: <4F47CAF5.4000709@arm.com>
On Fri, Feb 24, 2012 at 05:37:57PM +0000, Marc Zyngier wrote:
> > This patch relies on the fact that the HAVE_SCHED_CLOCK config option no
> > longer exists. We could push it in if the patch had that option added to
> > the Kconfig, but then it would conflict with the removal of the Kconfig
> > by 6905a65 (ARM: Make the sched_clock framework mandatory, 2012-01-18).
>
> Ah! Indeed, you're perfectly right.
>
> > So I guess we send it through the arm-soc tree?
>
> I don't think arm-soc tracks rmk/for-next, so this has to go via
> Russell's tree. I'll take the patch and send Russell another pull
> request then.
Thanks, Marc.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] msm: timer: Support sched_clock()
Date: Fri, 24 Feb 2012 17:10:00 -0800 [thread overview]
Message-ID: <20120225011000.GA4611@codeaurora.org> (raw)
In-Reply-To: <4F47CAF5.4000709@arm.com>
On Fri, Feb 24, 2012 at 05:37:57PM +0000, Marc Zyngier wrote:
> > This patch relies on the fact that the HAVE_SCHED_CLOCK config option no
> > longer exists. We could push it in if the patch had that option added to
> > the Kconfig, but then it would conflict with the removal of the Kconfig
> > by 6905a65 (ARM: Make the sched_clock framework mandatory, 2012-01-18).
>
> Ah! Indeed, you're perfectly right.
>
> > So I guess we send it through the arm-soc tree?
>
> I don't think arm-soc tracks rmk/for-next, so this has to go via
> Russell's tree. I'll take the patch and send Russell another pull
> request then.
Thanks, Marc.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-02-25 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 1:39 [PATCH] msm: timer: Support sched_clock() Stephen Boyd
2012-02-22 1:39 ` Stephen Boyd
2012-02-22 21:55 ` David Brown
2012-02-22 21:55 ` David Brown
2012-02-24 10:11 ` Marc Zyngier
2012-02-24 10:11 ` Marc Zyngier
2012-02-24 17:09 ` David Brown
2012-02-24 17:09 ` David Brown
2012-02-24 17:24 ` Marc Zyngier
2012-02-24 17:24 ` Marc Zyngier
2012-02-24 17:32 ` Stephen Boyd
2012-02-24 17:32 ` Stephen Boyd
2012-02-24 17:37 ` Marc Zyngier
2012-02-24 17:37 ` Marc Zyngier
2012-02-25 1:10 ` David Brown [this message]
2012-02-25 1:10 ` David Brown
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=20120225011000.GA4611@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=sboyd@codeaurora.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.