From: Marek Behun <marek.behun@nic.cz>
To: u-boot@lists.denx.de
Subject: [PATCH 10/10] setexpr: Add support for strings
Date: Thu, 5 Nov 2020 18:50:06 +0100 [thread overview]
Message-ID: <20201105185006.5e2fa8eb@nic.cz> (raw)
In-Reply-To: <CAPnjgZ3DmeaincEcYkjeTuRijqtMZhJiDnyx_o4eSRE4gJaVFw@mail.gmail.com>
On Thu, 5 Nov 2020 10:27:28 -0700
Simon Glass <sjg@chromium.org> wrote:
> I don't see how that works. The *10 thing in my example reads a string
> out of address 10.
/o\ ahaaaa, OK, that makes sense. So setexpr can dereference strings.
I didn't know about that, I thouth the resulting string would be
"*10*100".
In this case
Acked-by: Marek Beh?n <marek.behun@nic.cz>
next prev parent reply other threads:[~2020-11-05 17:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 21:15 [PATCH 00/10] setexpr: Correct various bugs and add tests plus string support Simon Glass
2020-11-01 21:15 ` [PATCH 01/10] test: Add some tests for setexpr Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 02/10] command: Add constants for cmd_get_data_size string / error Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 03/10] setexpr: Add explicit support for 32- and 64-bit ints Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 04/10] test: Add some setexpr regex tests Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 05/10] setexpr: Split the core logic into its own function Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 06/10] setexpr: Add some tests for buffer overflow and backref Simon Glass
2020-12-02 21:23 ` Tom Rini
2021-01-17 22:52 ` CRASH caused by: " Heinrich Schuchardt
2021-01-19 18:06 ` Simon Glass
2021-01-19 19:07 ` Heinrich Schuchardt
2021-01-19 19:45 ` Tom Rini
2021-01-20 0:17 ` Simon Glass
2020-11-01 21:15 ` [PATCH 07/10] setexpr: Correct dropping of final unmatched string Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 08/10] setexpr: Correct buffer overflow bug and enable tests Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 09/10] setexpr: Convert to use a struct for values Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 10/10] setexpr: Add support for strings Simon Glass
2020-11-01 23:08 ` Marek Behun
2020-11-03 15:12 ` Simon Glass
2020-11-03 16:30 ` Marek Behun
2020-11-05 16:49 ` Wolfgang Denk
2020-11-05 17:27 ` Simon Glass
2020-11-06 20:58 ` Tom Rini
2020-11-06 21:48 ` Simon Glass
2020-11-05 16:47 ` Wolfgang Denk
2020-11-05 17:27 ` Simon Glass
2020-11-05 17:50 ` Marek Behun [this message]
2020-11-05 19:10 ` Wolfgang Denk
2020-11-05 20:15 ` Simon Glass
2020-12-02 21:23 ` 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=20201105185006.5e2fa8eb@nic.cz \
--to=marek.behun@nic.cz \
--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