powerpc/syscalls: Use the number when building SPU syscall table
authorMichael Ellerman <mpe@ellerman.id.au>
Tue, 16 Jun 2020 13:56:16 +0000 (23:56 +1000)
committerMichael Ellerman <mpe@ellerman.id.au>
Wed, 17 Jun 2020 13:20:03 +0000 (23:20 +1000)
commit1497eea68624f6076bf3eaf66baec3771ea04045
treea7e4e2c539c7d2867cbe801e8cea02eb3430b8a6
parent687993ccf3b05070598b89fad97410b26d7bc9d2
powerpc/syscalls: Use the number when building SPU syscall table

Currently the macro that inserts entries into the SPU syscall table
doesn't actually use the "nr" (syscall number) parameter.

This does work, but it relies on the exact right number of syscall
entries being emitted in order for the syscal numbers to line up with
the array entries. If for example we had two entries with the same
syscall number we wouldn't get an error, it would just cause all
subsequent syscalls to be off by one in the spu_syscall_table.

So instead change the macro to assign to the specific entry of the
array, meaning any numbering overlap will be caught by the compiler.

Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Link: https://lore.kernel.org/r/20200616135617.2937252-1-mpe@ellerman.id.au
arch/powerpc/platforms/cell/spu_callbacks.c