From: Paul Kocialkowski <contact@paulk.fr>
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 21:36:38 +0200 [thread overview]
Message-ID: <1434396998.2324.55.camel@collins> (raw)
In-Reply-To: <20150615160210.GY1728@bill-the-cat>
Le lundi 15 juin 2015 ? 12:02 -0400, Tom Rini a ?crit :
> On Mon, Jun 15, 2015 at 08:59:47AM -0600, Stephen Warren wrote:
> > 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.
>
> Yes. Also numbers are hex by default in U-Boot so we don't need the 0x
> here.
Thanks for the reminder. v3 doesn't include the 0x.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150615/f0a1a61b/attachment.sig>
next prev parent reply other threads:[~2015-06-15 19:36 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
2015-06-15 16:02 ` Tom Rini
2015-06-15 19:36 ` Paul Kocialkowski [this message]
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=1434396998.2324.55.camel@collins \
--to=contact@paulk.fr \
--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