From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] common: cmd_part: start and size sub-commands introduction
Date: Mon, 15 Jun 2015 08:59:47 -0600 [thread overview]
Message-ID: <557EE863.8030501@wwwdotorg.org> (raw)
In-Reply-To: <1434184697-23410-3-git-send-email-contact@paulk.fr>
On 06/13/2015 02:38 AM, Paul Kocialkowski wrote:
> This introduces the part start and part size sub-commands. The purpose of these
> is to store the start block and size of a partition in a variable, given the
> device and partition number.
>
> This allows reading raw data that fits a single partition more easily.
> For instance, this could be used to figure out the start block and size of a
> kernel partition when a partition table is present, given the partition number.
Patches 1 and 2,
Acked-by: Stephen Warren <swarren@nvidia.com>
One minor comment here though:
> diff --git a/common/cmd_part.c b/common/cmd_part.c
> +static int do_part_start(int argc, char * const argv[])
> + if (argc < 4)
> + return CMD_RET_USAGE;
...
> + snprintf(buf, sizeof(buf), "0x%lx", info.start);
> + setenv(argv[3], buf);
It would be nice if the variable name parameter to this command (and
part size) were optional, just like it is in "part uuid". This would
make it simpler to run the command interactively while experimenting.
next prev parent reply other threads:[~2015-06-15 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 8:38 [U-Boot] [PATCH v2 0/3] common: cmd_part: start and size sub-commands introduction Paul Kocialkowski
2015-06-13 8:38 ` [U-Boot] [PATCH v2 1/3] common: cmd_part: Proper alignment Paul Kocialkowski
2015-06-13 8:38 ` [U-Boot] [PATCH v2 2/3] common: cmd_part: start and size sub-commands introduction Paul Kocialkowski
2015-06-15 14:59 ` Stephen Warren [this message]
2015-06-15 16:02 ` Tom Rini
2015-06-15 19:36 ` Paul Kocialkowski
2015-06-15 16:13 ` Paul Kocialkowski
2015-06-13 8:38 ` [U-Boot] [PATCH v2 3/3] common: cmd_part: Error prints on failures Paul Kocialkowski
2015-06-15 15:00 ` Stephen Warren
2015-06-15 19:25 ` Paul Kocialkowski
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=557EE863.8030501@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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