From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] scalable TWD localtimer
Date: Fri, 03 Jun 2011 11:51:48 +0530 [thread overview]
Message-ID: <4DE87D7C.60609@ti.com> (raw)
In-Reply-To: <BANLkTikYRk6ZKaZnTt4NFiDSnbN+jyNT-Q@mail.gmail.com>
On 6/3/2011 11:46 AM, Colin Cross wrote:
> On Thu, Jun 2, 2011 at 10:26 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
>> Linus,
>>
[...]
>
> I will submit the Tegra clock change along with a separate series.
> This change should not change any functionality on platforms where the
> clock has not been defined, so there is no need to sequence it with
> clock patches.
Agree. My intention was same bug get fixed on all platforms together
in one series. Ofcourse the platform non supporting CPUFreq in mainline
shouldn't care too much either.
Sorry for noise.
Regards
Santosh
prev parent reply other threads:[~2011-06-03 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 22:01 [GIT PULL] scalable TWD localtimer Linus Walleij
2011-06-03 5:26 ` Santosh Shilimkar
2011-06-03 6:16 ` Colin Cross
2011-06-03 6:21 ` Santosh Shilimkar [this message]
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=4DE87D7C.60609@ti.com \
--to=santosh.shilimkar@ti.com \
--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