Re: [guv v2 08/31] tracing: Replace __get_cpu_var uses

2013-08-30 Thread Ingo Molnar
* Christoph Lameter wrote: > On Wed, 28 Aug 2013, Steven Rostedt wrote: > > > You should limit the width of the change log to 76 characters. > > > > I fixed it for now. > > Ok. I have to do that to all patches though. Next rollup. You'll also need to fix the preempt debug checks before spread

Re: [guv v2 08/31] tracing: Replace __get_cpu_var uses

2013-08-29 Thread Christoph Lameter
On Wed, 28 Aug 2013, Steven Rostedt wrote: > You should limit the width of the change log to 76 characters. > > I fixed it for now. Ok. I have to do that to all patches though. Next rollup. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to ma

Re: [guv v2 08/31] tracing: Replace __get_cpu_var uses

2013-08-28 Thread Masami Hiramatsu
(2013/08/29 4:48), Steven Rostedt wrote: > On Mon, 26 Aug 2013 20:44:37 + > Christoph Lameter wrote: > >> __get_cpu_var() is used for multiple purposes in the kernel source. One of >> them is >> address calculation via the form &__get_cpu_var(x). This calculates the >> address for >> the in

Re: [guv v2 08/31] tracing: Replace __get_cpu_var uses

2013-08-28 Thread Steven Rostedt
On Mon, 26 Aug 2013 20:44:37 + Christoph Lameter wrote: > __get_cpu_var() is used for multiple purposes in the kernel source. One of > them is > address calculation via the form &__get_cpu_var(x). This calculates the > address for > the instance of the percpu variable of the current process

[guv v2 08/31] tracing: Replace __get_cpu_var uses

2013-08-26 Thread Christoph Lameter
__get_cpu_var() is used for multiple purposes in the kernel source. One of them is address calculation via the form &__get_cpu_var(x). This calculates the address for the instance of the percpu variable of the current processor based on an offset. Others usage cases are for storing and retrievin