All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: opensbi@lists.infradead.org
Subject: [PATCH] lib: sbi: sbi_ecall: Improve return SBI error
Date: Wed, 22 Feb 2023 08:42:48 +0000	[thread overview]
Message-ID: <Y/XViK1LimqbfwSx@APC323> (raw)
In-Reply-To: <2c3c52436f6dadf09fe733a257a46943ff57728a.camel@126.com>

On Tue, Feb 21, 2023 at 07:34:46PM +0800, Xiang W wrote:
> ? 2023-02-21???? 18:47 +0800?Yu Chien Peter Lin???
> > We should also check if the return error code is greater than 0
> > (SBI_SUCCESS), as this is an invalid error.
> > 
> > Also rename the variable returned via a0 to 'out_err' and use
> > SBI_ERR_NOT_SUPPORTED when the extension does not have a handler
> > for consistency with the standard SBI errors defined in Table 1
> > of the SBI specification.
> > 
> > Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> > ---
> > ?lib/sbi/sbi_ecall.c | 18 +++++++++---------
> > ?1 file changed, 9 insertions(+), 9 deletions(-)
> > 
> > diff --git a/lib/sbi/sbi_ecall.c b/lib/sbi/sbi_ecall.c
> > index 27ce5d49..8accf675 100644
> > --- a/lib/sbi/sbi_ecall.c
> > +++ b/lib/sbi/sbi_ecall.c
> > @@ -97,34 +97,34 @@ void sbi_ecall_unregister_extension(struct sbi_ecall_extension *ext)
> > ?
> > ?int sbi_ecall_handler(struct sbi_trap_regs *regs)
> > ?{
> > -???????int ret = 0;
> > +???????int out_err = 0;
> There is no need to rename ret to out_err because a0 is not always an
> error code in legacy extensions
> Other than the above, it looks good to me.
> 
> Reviewed-by: Xiang W <wxjstz@126.com>

Hi Xiang, Andrew,

Thanks for the review,
Sure I'll use 'ret' as it is in next patch.

Best regards,
Peter Lin


  reply	other threads:[~2023-02-22  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 10:47 [PATCH] lib: sbi: sbi_ecall: Improve return SBI error Yu Chien Peter Lin
2023-02-21 11:34 ` Xiang W
2023-02-22  8:42   ` Yu-Chien Peter Lin [this message]
2023-02-21 17:21 ` Andrew Jones
2023-02-21 17:23   ` Anup Patel
2023-02-21 18:07     ` Andrew Jones
2023-02-22  3:29       ` Anup Patel

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=Y/XViK1LimqbfwSx@APC323 \
    --to=peterlin@andestech.com \
    --cc=opensbi@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.