From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: delete empty sleep.S
Date: Wed, 03 Oct 2012 09:25:15 -0600 [thread overview]
Message-ID: <506C58DB.2020307@wwwdotorg.org> (raw)
In-Reply-To: <1349230006.3783.7.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
On 10/02/2012 08:06 PM, Joseph Lo wrote:
> On Wed, 2012-10-03 at 07:21 +0800, Stephen Warren wrote:
>> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> sleep.S doesn't provide anything useful any more; commit b4e395b "ARM:
>> tegra: Remove flow controller programming" removed the last public code
>> here, so that everyting that was left was just macros or #includes.
>>
>> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> ---
>
> Hi Stephen,
>
> Just let you know.
> I may update this file later for CPU idle LP2 support. Anyway, it's OK
> to me to re-add this file when introducing CPU idle LP2 support as well.
Wouldn't the code go in sleep-t20.S, sleep-t30.S, or cpuidle.c anyway?
But yes, I think removing the file until there's actually content should
be fine.
next prev parent reply other threads:[~2012-10-03 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 23:21 [PATCH] ARM: tegra: delete empty sleep.S Stephen Warren
[not found] ` <1349220069-4051-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-03 2:06 ` Joseph Lo
[not found] ` <1349230006.3783.7.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2012-10-03 15:25 ` Stephen Warren [this message]
[not found] ` <506C58DB.2020307-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-15 17:37 ` Stephen Warren
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=506C58DB.2020307@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.