Re: [PATCH 2/9] MIPS OCTEON Enable use of FPU

[David Daney <ddaney@caviumnetworks.com>]

On 01/11/2015 11:06 PM, Abhishek Paliwal wrote:
> commit  a36d8225bceba4b7be47ade34d175945f85cffbc upstream

Why are you spamming us with this?  We don't need to know what you are 
cherry-picking.


>
> Some versions of the assembler will not assemble CFC1 for OCTEON, so override the ISA for these.
>
> Add r4k_fpu.o to handle low level FPU initialization.
>
> Modify octeon_switch.S to save the FPU registers. And include r4k_switch.S to pick up more FPU support.
>
> Get rid of "#define cpu_has_fpu 0"
>
> Signed-off-by: David Daney <david.daney@cavium.com>
> Signed-off-by: Andreas Herrmann <andreas.herrmann@caviumnetworks.com>
> Cc: linux-mips@linux-mips.org
> Cc: James Hogan <james.hogan@imgtec.com>
> Cc: kvm@vger.kernel.org
> Patchwork: https://patchwork.linux-mips.org/patch/7006/
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
> Signed-off-by: Abhishek Paliwal <abhishek.paliwal@aricent.com>
> ---
>   .../asm/mach-cavium-octeon/cpu-feature-overrides.h |  1 -
>   arch/mips/kernel/Makefile                          |  2 +-
>   arch/mips/kernel/branch.c                          |  6 +-
>   arch/mips/kernel/octeon_switch.S                   | 85 ++++++++++++++++------
>   arch/mips/kernel/r4k_switch.S                      |  3 +
>   arch/mips/math-emu/cp1emu.c                        | 12 ++-
>   6 files changed, 80 insertions(+), 29 deletions(-)
>
[...]
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

I wrote the patch, what gives you the right to say that it is "... 
proprietary to Aricent ..."?   Nothing.  We really must insist that you 
quit making this type of misrepresentation.

David Daney

>