Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190703001842.12238-1-alistair.francis@wdc.com> <20190703001842.12238-2-alistair.francis@wdc.com>
In-Reply-To: <20190703001842.12238-2-alistair.francis@wdc.com>
From:   Arnd Bergmann <arnd@arndb.de>
Date:   Wed, 3 Jul 2019 10:31:11 +0200
Message-ID: <CAK8P3a1LkapKKbwEKnX57YricbAkPLCpqSTXnpL7grVYauSLSw@mail.gmail.com>
Subject: Re: [PATCH 1/2] uapi/asm-generic: Allow defining a custom __SIGINFO struct
To:     Alistair Francis <alistair.francis@wdc.com>
Cc:     linux-riscv-bounces@lists.infradead.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Alistair Francis <alistair23@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Jul 3, 2019 at 2:21 AM Alistair Francis
<alistair.francis@wdc.com> wrote:
>
> Allow defining a custom __SIGINFO struct. This allows architectures to
> apply their own padding and allignment requirements to the struct. This
> is similar to the __ARCH_SI_ATTRIBUTES #define that already exists, but
> applies to the __SIGINFO struct instead of the siginfo_t struct.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>

I don't think there should be another special case for rv32 here,
we already have too many exceptions for architectures that
were different for no good reason.

Please keep the same definition that everything else has.

       Arnd