From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] the weirdness with cmd_df.c
Date: Mon, 4 Feb 2013 17:00:25 +0100 [thread overview]
Message-ID: <20130204170025.6971548c@lilith> (raw)
In-Reply-To: <20130204105405.17762a72v8atypa8@crashcourse.ca>
Hi Robert,
On Mon, 04 Feb 2013 10:54:05 -0500, "Robert P. J. Day"
<rpjday@crashcourse.ca> wrote:
> i mentioned this this weekend as well, can someone clarify this?
> the source file cmd_df.c looks weird:
>
> U_BOOT_CMD(
> sf, 2, 1, do_serial_flash,
> "Serial flash sub-system",
> "probe [bus:]cs - init flash device on given SPI bus and CS")
>
> so the source file "cmd_df.c" allegedly defines a command called "sf",
> which invokes "do_serial_flash", which isn't even defined in that
> source file -- what's defined in that file is "do_df". i don't see
> "do_serial_flash" defined anywhere in the u-boot source tree. am i
> just being blind? i see no reference to that source file in Makefile,
> so i'm guessing it's historical cruft that could be deleted?
do_serial_flash() indeed does not appear anywhere. As for deleting, you
should check which makefile builds cmd_df.c, under which condition,
and if this condition is met in any U-Boot MAKEALL target. If not, just
submit a patch to remove cmd_df.c from the baseline.
BTW: IMO, you should just submit a patch instead of asking. If the patch
is ok, it'll be taken, and you didn't have anything to ask; if the
patch is not OK, the one who NAKs it will tell you why, and you'll get
the answer without asking. :)
Amicalement,
--
Albert.
prev parent reply other threads:[~2013-02-04 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 15:54 [U-Boot] the weirdness with cmd_df.c Robert P. J. Day
2013-02-04 16:00 ` Albert ARIBAUD [this message]
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=20130204170025.6971548c@lilith \
--to=albert.u.boot@aribaud.net \
--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