U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] EXT4: Fix number base handling of "ext4write" command
Date: Fri, 31 Jan 2014 12:26:49 +0100	[thread overview]
Message-ID: <20140131112650.0598438242A@gemini.denx.de> (raw)
In-Reply-To: <20140131110818.07d79eac@amdc2363>

Dear Lukasz,

In message <20140131110818.07d79eac@amdc2363> you wrote:
> 
> > I do not see any such need.  Hex input base is the established and
> > documented default - ext4write is not a special command, so why should
> > we mention this here when we do not mention it anywhere else?
> 
> If now all <fs>*write and <fs>*load commands accept only hex input,
> then I agree, that extra comment is not needed.

Not only these, but all other commands - with the inglorious exception
of the "sleep" command (but hey - there must be a bad example
somewhere, right? ;-)

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
There are two ways of constructing a software design. One way  is  to
make  it  so  simple that there are obviously no deficiencies and the
other is to make it so complicated that there are  no  obvious  defi-
ciencies.                             - Charles Anthony Richard Hoare

  reply	other threads:[~2014-01-31 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  8:28 [U-Boot] [PATCH] EXT4: Fix number base handling of "ext4write" command Wolfgang Denk
2014-01-31  9:27 ` Lukasz Majewski
2014-01-31  9:45   ` Wolfgang Denk
2014-01-31 10:08     ` Lukasz Majewski
2014-01-31 11:26       ` Wolfgang Denk [this message]
2014-02-19 15:49 ` [U-Boot] " 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=20140131112650.0598438242A@gemini.denx.de \
    --to=wd@denx.de \
    --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