Re: [PATCH v4 08/12] mips: Get rid of custom mips ABIs for syscall tables

Next message: Satish Kharat: "[PATCH net-next v13 10/11] enic: add V2 VF probe with admin channel and PF registration"
Previous message: Namhyung Kim: "Re: [PATCH v8 6/9] perf c2c: add function view hierarchy entry creation"
In reply to: Arnd Bergmann: "Re: [PATCH v4 08/12] mips: Get rid of custom mips ABIs for syscall tables"
Next in thread: Arnd Bergmann: "Re: [PATCH v4 08/12] mips: Get rid of custom mips ABIs for syscall tables"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: André Almeida

Date: Wed Aug 12 2026 - 09:08:41 EST

Em 12/08/2026 06:16, Arnd Bergmann escreveu:

On Wed, Aug 12, 2026, at 05:33, André Almeida wrote:

Get rid of the mips exclusive ABIs for the syscall tables and replace them
with the common ABI names, replacing n32 and o32 with 32 and n64 with 64.

No functional change happens, but it simplifies and helps to unify the
tables.

Signed-off-by: André Almeida <andrealmeid@xxxxxxxxxx>

I had expected you to use 'common' instead of '32' and '64' here. Since you
did not combine the n32/n64 tables, this makes no practical difference,
but it still makes the tables look different from all the other ones, and
it means that the following patch to unify the tables is harder to
validate since the inputs are still not line-identical.

Is there some reason you went with this approach?

Ops, no good reason here, it was a mistake :) I will redo it to use common from [1, 211] syscalls. What about o32? Should I kept it as o32, giving that it doesn't make much difference?