[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1374259073.3356.22.camel@gandalf.local.home>
Date: Fri, 19 Jul 2013 14:37:53 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuah Khan <shuah.kh@...sung.com>
Cc: "len.brown@...el.com" <len.brown@...el.com>,
"pavel@....cz" <pavel@....cz>, "rjw@...k.pl" <rjw@...k.pl>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"fweisbec@...il.com" <fweisbec@...il.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"paul.gortmaker@...driver.com" <paul.gortmaker@...driver.com>,
"joe@...ches.com" <joe@...ches.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"shuahkhan@...il.com" <shuahkhan@...il.com>
Subject: Re: [PATCH v5] power: new trace event to print device suspend and
resume time
On Fri, 2013-07-19 at 18:29 +0000, Shuah Khan wrote:
> Tried with temp variables. Patch is on its way with temp variables. I
> generated .s with and without temp variables and didn't see any
> difference. Should I be seeing a difference, if so what am I missing?
>
> In any case, you have the patch v6 with temp variables.
>
There may not be, matters how good gcc is in optimization.
Temp variables are fine to keep if they work.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists