From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
linuxppc-dev@ozlabs.org
Cc: linux-arch@ozlabs.org, linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH 1/2] powerpc/syscalls: Use the number when building SPU syscall table
Date: Sun, 21 Jun 2020 20:13:17 +1000 [thread overview]
Message-ID: <875zbkd8w2.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <159248379723.3471720.7761730589256580141.b4-ty@ellerman.id.au>
Michael Ellerman <patch-notifications@ellerman.id.au> writes:
> On Tue, 16 Jun 2020 23:56:16 +1000, Michael Ellerman wrote:
>> 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.
>>
>> [...]
>
> Applied to powerpc/fixes.
>
> [1/2] powerpc/syscalls: Use the number when building SPU syscall table
> https://git.kernel.org/powerpc/c/1497eea68624f6076bf3eaf66baec3771ea04045
> [2/2] powerpc/syscalls: Split SPU-ness out of ABI
> https://git.kernel.org/powerpc/c/35e32a6cb5f694fda54a5f391917e4ceefa0fece
Patch 2 dropped.
cheers
prev parent reply other threads:[~2020-06-21 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 13:56 [PATCH 1/2] powerpc/syscalls: Use the number when building SPU syscall table Michael Ellerman
2020-06-16 13:56 ` [PATCH 2/2] powerpc/syscalls: Split SPU-ness out of ABI Michael Ellerman
2020-06-19 10:26 ` Michael Ellerman
2020-06-19 12:07 ` Arnd Bergmann
2020-06-18 12:37 ` [PATCH 1/2] powerpc/syscalls: Use the number when building SPU syscall table Michael Ellerman
2020-06-21 10:13 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zbkd8w2.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=linux-arch@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=patch-notifications@ellerman.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox