From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: clps711x: Use linux/sched_clock.h
Date: Fri, 11 Oct 2013 14:53:41 -0700 [thread overview]
Message-ID: <87bo2v8oey.fsf@linaro.org> (raw)
In-Reply-To: <1380829783-876-1-git-send-email-sboyd@codeaurora.org> (Stephen Boyd's message of "Thu, 3 Oct 2013 12:49:42 -0700")
Hi Stephen,
Stephen Boyd <sboyd@codeaurora.org> writes:
> The sched_clock.h include is under include/linux now.
>
> Cc: Alexander Shiyan <shc_work@mail.ru>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
I applied both of these to next/cleanup.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
Alexander Shiyan <shc_work@mail.ru>
Subject: Re: [PATCH 1/2] ARM: clps711x: Use linux/sched_clock.h
Date: Fri, 11 Oct 2013 14:53:41 -0700 [thread overview]
Message-ID: <87bo2v8oey.fsf@linaro.org> (raw)
In-Reply-To: <1380829783-876-1-git-send-email-sboyd@codeaurora.org> (Stephen Boyd's message of "Thu, 3 Oct 2013 12:49:42 -0700")
Hi Stephen,
Stephen Boyd <sboyd@codeaurora.org> writes:
> The sched_clock.h include is under include/linux now.
>
> Cc: Alexander Shiyan <shc_work@mail.ru>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
I applied both of these to next/cleanup.
Thanks,
Kevin
next prev parent reply other threads:[~2013-10-11 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 19:49 [PATCH 1/2] ARM: clps711x: Use linux/sched_clock.h Stephen Boyd
2013-10-03 19:49 ` Stephen Boyd
2013-10-03 19:49 ` [PATCH 2/2] ARM: Remove temporary sched_clock.h header Stephen Boyd
2013-10-03 19:49 ` Stephen Boyd
2013-10-11 21:53 ` Kevin Hilman [this message]
2013-10-11 21:53 ` [PATCH 1/2] ARM: clps711x: Use linux/sched_clock.h Kevin Hilman
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=87bo2v8oey.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.