[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250613165226.751541c6@pumpkin>
Date: Fri, 13 Jun 2025 16:52:26 +0100
From: David Laight <david.laight.linux@...il.com>
To: Radim Krčmář <rkrcmar@...tanamicro.com>
Cc: <linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, "Paul
Walmsley" <paul.walmsley@...ive.com>, "Palmer Dabbelt"
<palmer@...belt.com>, "Albert Ou" <aou@...s.berkeley.edu>, "Alexandre
Ghiti" <alex@...ti.fr>, "Atish Patra" <atishp@...osinc.com>, "Andrew Jones"
<ajones@...tanamicro.com>, Clément Léger
<cleger@...osinc.com>, "Anup Patel" <apatel@...tanamicro.com>
Subject: Re: [PATCH 2/2] RISC-V: make use of variadic sbi_ecall
On Fri, 13 Jun 2025 16:10:52 +0200
Radim Krčmář <rkrcmar@...tanamicro.com> wrote:
...
> The macro will result in the same arguments as before, and it is what
> the sbi_ecall actually should do.
Ugg...
Are you using pre-processor 'magic' to add a pile of zeros and then
select the first 'n' arguments?
That ought to be banned as error prone.
I think the one for strncpy() removes the immediate compile error for:
strncpy(dest, src, 1, 2);
David
Powered by blists - more mailing lists