From: Michal Simek <michal.simek@amd.com>
To: Tom Rini <trini@konsulko.com>, Love Kumar <love.kumar@amd.com>
Cc: Angelo Dureghello <angelo@kernel-space.org>,
u-boot@lists.denx.de, git@xilinx.com, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH v3] test/py: reset: Add a test for reset command
Date: Mon, 11 Mar 2024 15:52:57 +0100 [thread overview]
Message-ID: <9e3f916a-7e5b-4ec8-abe4-c2cead1df557@amd.com> (raw)
In-Reply-To: <20240311143938.GV1523872@bill-the-cat>
On 3/11/24 15:39, Tom Rini wrote:
> On Mon, Mar 11, 2024 at 02:40:59PM +0530, Love Kumar wrote:
>> Hi,
>>
>> On 11/03/24 2:11 pm, Angelo Dureghello wrote:
>>> Hi,
>>>
>>> jfyi,
>>>
>>> reset support added in qemu
>>> merged as commit d3c79c3974.
>>>
>>> Regards,
>>> angelo
>>>
>> The other issue was with echo commands:
>> => echo $modeboot
>> $modeboot
>>
>> => echo $?
>> $?
>>
>> Does HUSH shell is enabled by default for this?
>
> It is not, so at least the saveenv test needs to depend on HUSH_PARSER
> too.
Based on logs on this platform echo $? doesn't return any value.
There is any config for it which is not enabled for this platform.
Do you know which Kconfig symbol it is?
Depending on HUSH is likely big hammer but I was not able to find that exact
Kconfig symbol just for $?
thanks,
Michal
next prev parent reply other threads:[~2024-03-11 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 7:41 [PATCH v3] test/py: reset: Add a test for reset command Love Kumar
2024-02-20 20:04 ` Tom Rini
2024-03-02 15:18 ` Tom Rini
2024-03-03 21:58 ` Angelo Dureghello
2024-03-05 12:34 ` Michal Simek
2024-03-06 23:36 ` Angelo Dureghello
2024-03-07 0:10 ` Tom Rini
2024-03-07 7:56 ` Angelo Dureghello
2024-03-07 8:26 ` Michal Simek
2024-03-07 12:55 ` Tom Rini
2024-03-08 6:40 ` Angelo Dureghello
2024-03-11 8:41 ` Angelo Dureghello
2024-03-11 9:10 ` Love Kumar
2024-03-11 14:39 ` Tom Rini
2024-03-11 14:52 ` Michal Simek [this message]
2024-03-11 15:09 ` Tom Rini
2024-03-11 15:14 ` Michal Simek
2024-03-11 15:15 ` Tom Rini
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=9e3f916a-7e5b-4ec8-abe4-c2cead1df557@amd.com \
--to=michal.simek@amd.com \
--cc=angelo@kernel-space.org \
--cc=git@xilinx.com \
--cc=love.kumar@amd.com \
--cc=marex@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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