From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] common: fastboot: send FAIL if variable does not exist
Date: Thu, 12 Jun 2025 16:19:36 +0200 [thread overview]
Message-ID: <925212c2-6c48-402d-8301-e06b62061248@gmail.com> (raw)
In-Reply-To: <aEqK9IXf94hx9QnX@pengutronix.de>
On 12.06.2025 10:08, Sascha Hauer wrote:
> Hi Andrei,
>
> On Wed, Jun 11, 2025 at 07:56:45PM +0200, Andrei Lalaev wrote:
>> According to doc [1], new implementations should send FAIL if the
>> variable specified in the getvar command does not exist.
>>
>> [1]: https://android.googlesource.com/platform/system/core/+show/refs/heads/main/fastboot/README.md#121
>>
>> Signed-off-by: Andrei Lalaev <andrey.lalaev@gmail.com>
>> ---
>> common/fastboot.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/common/fastboot.c b/common/fastboot.c
>> index 56bc4e82c4..3df3c227a3 100644
>> --- a/common/fastboot.c
>> +++ b/common/fastboot.c
>> @@ -372,7 +372,7 @@ static void cb_getvar(struct fastboot *fb, const char *cmd)
>> goto out;
>>
>> skip_partitions:
>> - fastboot_tx_print(fb, FASTBOOT_MSG_OKAY, "");
>> + fastboot_tx_print(fb, FASTBOOT_MSG_FAIL, "");
>
> With this a "fastboot getvar all" fails.
>
> I fixed this up as below.
>
> Sascha
Hi,
Thanks a lot for the fix!
To be honest, I had only checked the original patch on Barebox 2025.02 and then
just backported it to the latest master :/
Would you be willing to take primary authorship for this commit?
Since you've reworked it completely, I think that would be more appropriate.
--
Best regards,
Andrei Lalaev
prev parent reply other threads:[~2025-06-12 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 17:56 Andrei Lalaev
2025-06-12 8:08 ` Sascha Hauer
2025-06-12 14:19 ` Andrei Lalaev [this message]
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=925212c2-6c48-402d-8301-e06b62061248@gmail.com \
--to=andrey.lalaev@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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