From: Michal Simek <michal.simek@amd.com>
To: Maarten Brock <Maarten.Brock@sttls.nl>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"git@amd.com" <git@amd.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Shantur Rathore <i@shantur.com>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v6 2/3] efi_var: Unify read/write access helper function
Date: Tue, 3 Feb 2026 12:45:55 +0100 [thread overview]
Message-ID: <e8526845-44c4-44ef-8921-bee95fbe2fe3@amd.com> (raw)
In-Reply-To: <GV2PR05MB1194157700C5D0ABCF1578C64839BA@GV2PR05MB11941.eurprd05.prod.outlook.com>
On 2/3/26 12:29, Maarten Brock wrote:
>> -----Original Message-----
>> From: Michal Simek <michal.simek@amd.com>
>> Sent: Tuesday 3 February 2026 11:10
>> To: Maarten Brock <Maarten.Brock@sttls.nl>; u-boot@lists.denx.de;
>> git@amd.com
>> Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>; Heinrich Schuchardt
>> <xypron.glpk@gmx.de>; Shantur Rathore <i@shantur.com>; Tom Rini
>> <trini@konsulko.com>
>> Subject: Re: [PATCH v6 2/3] efi_var: Unify read/write access helper function
>>
>> Hi,
>>
>> On 2/3/26 10:44, Maarten Brock wrote:
>>> Hello Michal,
>>>
>>> Why are the new function names non-symmetrical?
>>> efi_var_to_storage <-> efi_var_from ...
>>
>> Ilias was asking about these names in v5 review.
>
> I'm sure he meant something different from what you implemented.
>
>> I am ok with this with a small nit.
>> Can we rename efi_var_read/write to efi_var_from/to_storage? I want to
>> make it clealer what these functions are used for
>>
>> With the changes above
>> Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
>
> I think Ilias meant to use:
> efi_var_from_storage & efi_var_to_storage
> and not:
> efi_var_from & efi_var_to_storage
You are likely right. Let me fix that.
Thanks,
Michal
next prev parent reply other threads:[~2026-02-03 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 7:57 [PATCH v6 0/3] efi_vars: Implement SPI Flash storage for EFI Michal Simek
2026-02-03 7:57 ` [PATCH v6 1/3] efi_var_file: refactor to move buffer functions Michal Simek
2026-02-03 7:57 ` [PATCH v6 2/3] efi_var: Unify read/write access helper function Michal Simek
2026-02-03 9:44 ` Maarten Brock
2026-02-03 10:10 ` Michal Simek
2026-02-03 11:29 ` Maarten Brock
2026-02-03 11:45 ` Michal Simek [this message]
2026-02-04 12:07 ` Ilias Apalodimas
2026-02-04 12:10 ` Michal Simek
2026-02-03 7:57 ` [PATCH v6 3/3] efi_vars: Implement SPI Flash store Michal Simek
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=e8526845-44c4-44ef-8921-bee95fbe2fe3@amd.com \
--to=michal.simek@amd.com \
--cc=Maarten.Brock@sttls.nl \
--cc=git@amd.com \
--cc=i@shantur.com \
--cc=ilias.apalodimas@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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