From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Could you include clockevents/clocksource tree in linux-next ?
Date: Thu, 19 Dec 2013 22:24:01 +0100 [thread overview]
Message-ID: <52B363F1.2080209@linaro.org> (raw)
Hi Stephen,
is it possible to add the clockevents/clocksource tree in linux-next.
git://git.linaro.org/people/daniel.lezcano/linux.git clockevents/next
It will be based on top of tip/timers/core.
Thanks
-- Daniel
--
<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
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: Could you include clockevents/clocksource tree in linux-next ?
Date: Thu, 19 Dec 2013 22:24:01 +0100 [thread overview]
Message-ID: <52B363F1.2080209@linaro.org> (raw)
Hi Stephen,
is it possible to add the clockevents/clocksource tree in linux-next.
git://git.linaro.org/people/daniel.lezcano/linux.git clockevents/next
It will be based on top of tip/timers/core.
Thanks
-- Daniel
--
<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 reply other threads:[~2013-12-19 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 21:24 Daniel Lezcano [this message]
2013-12-19 21:24 ` Could you include clockevents/clocksource tree in linux-next ? Daniel Lezcano
2013-12-19 22:39 ` Stephen Rothwell
2013-12-19 22:39 ` Stephen Rothwell
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=52B363F1.2080209@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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.