From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Rasmus Villemoes <ravi@prevas.dk>, u-boot@lists.u-boot-project.org
Cc: Igor Opaniuk <igor.opaniuk@gmail.com>,
Tom Rini <trini@konsulko.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Rasmus Villemoes <ravi@prevas.dk>
Subject: Re: [PATCH 1/3] cmd: optee_rpmb: sanitize TEE_ERROR -> E* translations
Date: Wed, 02 Sep 2026 14:45:41 +0200 [thread overview]
Message-ID: <87cxuvn7nu.fsf@kernel.org> (raw)
In-Reply-To: <20260828105005.200338-2-ravi@prevas.dk>
Hi Rasmus,
Thank you for the patch.
On Fri, Aug 28, 2026 at 12:50, Rasmus Villemoes <ravi@prevas.dk> wrote:
> Do not translate both OUT_OF_MEMORY and STORAGE_NO_SPACE to -ENOSPC;
> we have -ENOMEM which is more fitting for the former.
>
> Similarly, -ENOENT is a better match for ITEM_NOT_FOUND than "some IO
> went wrong".
>
> None of the callers currently care about the actual error code, so
> this makes no functional change, but we will add special handling of
> the -ENOSPC in a later patch.
>
> Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> ---
> cmd/optee_rpmb.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2026-09-02 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 10:50 [PATCH 0/3] avb: start handling too small buffer for reading persistent values Rasmus Villemoes
2026-08-28 10:50 ` [PATCH 1/3] cmd: optee_rpmb: sanitize TEE_ERROR -> E* translations Rasmus Villemoes
2026-09-02 12:45 ` Mattijs Korpershoek [this message]
2026-09-02 12:51 ` Rasmus Villemoes
2026-08-28 10:50 ` [PATCH 2/3] cmd: optee_rpmb: try to allocate large enough buffer when reading persistent value Rasmus Villemoes
2026-09-02 12:55 ` Mattijs Korpershoek
2026-08-28 10:50 ` [PATCH 3/3] avb_verify: read_persistent_value: honour contract regarding too small buffer Rasmus Villemoes
2026-09-02 13:03 ` Mattijs Korpershoek
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=87cxuvn7nu.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=igor.opaniuk@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=ravi@prevas.dk \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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.