Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-09-01 Thread Suresh Siddha
On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov wrote: > Hello, > > Who can review this? And where should I send FPU changes? > > And it seems that nobody cares about 2 fixes I sent before. > Linus, I understand that you won't take them into v3.17, but > perhaps you can ack/nack them explicitly?

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-09-01 Thread Suresh Siddha
On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov o...@redhat.com wrote: Hello, Who can review this? And where should I send FPU changes? And it seems that nobody cares about 2 fixes I sent before. Linus, I understand that you won't take them into v3.17, but perhaps you can ack/nack them

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/28, Ingo Molnar wrote: > > * H. Peter Anvin wrote: > > > Oleg, this is unacceptable. > > > > Last week was Kernel Summit and that was right on the heels of > > a merge window. We are backlogged like crazy and being rude > > doesn't help one iota. > > Also, the previous set of patches was

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/27, Linus Torvalds wrote: > > On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov wrote: > > > > Who can review this? And where should I send FPU changes? > > FWIW, I have nothing against this series (or, indeed, the last series > with the exception of 2/5 that got replaced by just the

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/27, H. Peter Anvin wrote: > > Oleg, this is unacceptable. > > Last week was Kernel Summit and that was right on the heels > of a merge window. We are backlogged like crazy and being > rude doesn't help one iota. Me? Rude?? I really hope that this is the first (and last) email from me

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Ingo Molnar
* H. Peter Anvin wrote: > Oleg, this is unacceptable. > > Last week was Kernel Summit and that was right on the heels of > a merge window. We are backlogged like crazy and being rude > doesn't help one iota. Also, the previous set of patches was under active review by Linus with

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Ingo Molnar
* H. Peter Anvin h...@zytor.com wrote: Oleg, this is unacceptable. Last week was Kernel Summit and that was right on the heels of a merge window. We are backlogged like crazy and being rude doesn't help one iota. Also, the previous set of patches was under active review by Linus with

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/27, H. Peter Anvin wrote: Oleg, this is unacceptable. Last week was Kernel Summit and that was right on the heels of a merge window. We are backlogged like crazy and being rude doesn't help one iota. Me? Rude?? I really hope that this is the first (and last) email from me which can

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/27, Linus Torvalds wrote: On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov o...@redhat.com wrote: Who can review this? And where should I send FPU changes? FWIW, I have nothing against this series (or, indeed, the last series with the exception of 2/5 that got replaced by just the

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-28 Thread Oleg Nesterov
On 08/28, Ingo Molnar wrote: * H. Peter Anvin h...@zytor.com wrote: Oleg, this is unacceptable. Last week was Kernel Summit and that was right on the heels of a merge window. We are backlogged like crazy and being rude doesn't help one iota. Also, the previous set of patches was

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread Linus Torvalds
On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov wrote: > > Who can review this? And where should I send FPU changes? FWIW, I have nothing against this series (or, indeed, the last series with the exception of 2/5 that got replaced by just the preemption disable). Although with the whole i387

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread H. Peter Anvin
Oleg, this is unacceptable. Last week was Kernel Summit and that was right on the heels of a merge window. We are backlogged like crazy and being rude doesn't help one iota. On August 27, 2014 11:51:38 AM PDT, Oleg Nesterov wrote: >Hello, > >Who can review this? And where should I send FPU

[PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread Oleg Nesterov
Hello, Who can review this? And where should I send FPU changes? And it seems that nobody cares about 2 fixes I sent before. Linus, I understand that you won't take them into v3.17, but perhaps you can ack/nack them explicitly? It seems that nobody can do this. Oleg.

[PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread Oleg Nesterov
Hello, Who can review this? And where should I send FPU changes? And it seems that nobody cares about 2 fixes I sent before. Linus, I understand that you won't take them into v3.17, but perhaps you can ack/nack them explicitly? It seems that nobody can do this. Oleg.

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread H. Peter Anvin
Oleg, this is unacceptable. Last week was Kernel Summit and that was right on the heels of a merge window. We are backlogged like crazy and being rude doesn't help one iota. On August 27, 2014 11:51:38 AM PDT, Oleg Nesterov o...@redhat.com wrote: Hello, Who can review this? And where should I

Re: [PATCH 0/4] x86, fpu: copy_process's FPU paths cleanups

2014-08-27 Thread Linus Torvalds
On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov o...@redhat.com wrote: Who can review this? And where should I send FPU changes? FWIW, I have nothing against this series (or, indeed, the last series with the exception of 2/5 that got replaced by just the preemption disable). Although with the