From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] time : pass broadcast device parameter
Date: Tue, 26 Feb 2013 12:30:28 +0100 [thread overview]
Message-ID: <512C9CD4.50808@linaro.org> (raw)
In-Reply-To: <CAKohpomqooF6DzzzdUFByA0wDxQ3RuPne15a9Vy1sScKjZfeyA@mail.gmail.com>
On 02/26/2013 09:45 AM, Viresh Kumar wrote:
> On 22 February 2013 03:31, Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>> The broadcast timer could be passed as parameter to the function
>> instead of using again tick_broadcast_device.evtdev which was
>> previously used in the caller function.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>
> I know you are going for another round with this patchset and was just
> trying v1.
>
> I did my tests on ARM Vexpress - TC2, big.LITTLE Arch.
>
> Tested-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks Viresh for testing.
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-02-26 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5123BE35.8070902@linaro.org>
[not found] ` <alpine.LFD.2.02.1302191904560.22263@ionos>
[not found] ` <5123C299.3080005@linaro.org>
2013-02-21 6:19 ` [resend] Timer broadcast question Santosh Shilimkar
2013-02-21 9:01 ` Daniel Lezcano
2013-02-21 9:14 ` Santosh Shilimkar
2013-02-21 22:01 ` [PATCH 1/2] time : pass broadcast device parameter Daniel Lezcano
2013-02-21 22:01 ` [PATCH 2/2][RFC] time : set broadcast irq affinity Daniel Lezcano
2013-02-22 17:55 ` Jacob Pan
2013-02-22 18:45 ` Thomas Gleixner
2013-02-25 22:50 ` Daniel Lezcano
2013-02-25 23:00 ` Jacob Pan
2013-02-26 8:45 ` [PATCH 1/2] time : pass broadcast device parameter Viresh Kumar
2013-02-26 11:30 ` Daniel Lezcano [this message]
2013-02-26 11:31 ` Daniel Lezcano
2013-02-26 12:14 ` Viresh Kumar
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=512C9CD4.50808@linaro.org \
--to=daniel.lezcano@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 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).