All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 9/9] Drop various features when the command line is not available
Date: Mon, 29 Feb 2016 16:47:19 -0700	[thread overview]
Message-ID: <56D4D887.2000303@wwwdotorg.org> (raw)
In-Reply-To: <1456459256-32643-10-git-send-email-sjg@chromium.org>

On 02/25/2016 09:00 PM, Simon Glass wrote:
> Some features are only useful or meaningful when the command line is
> present. Ensure that these features are not compiled in when CONFIG_CMDLINE
> is not enabled.

How does this series affect the various code that executes other U-Boot 
functionality by executing commands rather than calling functions? For 
instance, drivers/dfu/dfu_mmc.c:mmc_file_op() calls run_command() to 
perform the actual disk I/O. I assume that is incompatible with enabling 
this new feature? If so, can Kconfig enforce that?

  parent reply	other threads:[~2016-02-29 23:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  4:00 [U-Boot] [PATCH 0/9] Add CONFIG_CMDLINE to allow removal of all commands Simon Glass
2016-02-26  4:00 ` [U-Boot] [PATCH 1/9] cbfs: Update a function to be static Simon Glass
2016-02-26 17:16   ` Tom Rini
2016-02-26  4:00 ` [U-Boot] [PATCH 2/9] Add an option to enable the command line Simon Glass
2016-02-26 17:16   ` Tom Rini
2016-02-26  4:00 ` [U-Boot] [PATCH 3/9] arm: x86: Drop command-line code when CONFIG_CMDLINE is disabled Simon Glass
2016-02-26 17:16   ` Tom Rini
2016-02-26  4:00 ` [U-Boot] [PATCH 4/9] sandbox: Avoid calling commands when not available Simon Glass
2016-02-26 17:16   ` Tom Rini
2016-02-29 23:39   ` Stephen Warren
2016-03-03  0:25     ` Simon Glass
2016-03-03 16:58       ` Stephen Warren
2016-02-26  4:00 ` [U-Boot] [PATCH 5/9] Drop command-processing code when CONFIG_CMDLINE is disabled Simon Glass
2016-02-26 17:17   ` Tom Rini
2016-02-26  4:00 ` [U-Boot] [PATCH 6/9] Hang when no command line processing can be performed Simon Glass
2016-02-26 17:17   ` Tom Rini
2016-02-26 17:31     ` Simon Glass
2016-02-26 17:45       ` Tom Rini
2016-02-26  4:00 ` [U-Boot] [PATCH 7/9] Allow command code to compile to nothing Simon Glass
2016-02-26 17:17   ` Tom Rini
2016-02-29 23:40   ` Stephen Warren
2016-03-03  0:25     ` Simon Glass
2016-02-26  4:00 ` [U-Boot] [PATCH 8/9] Allow command-line files to be dropped Simon Glass
2016-02-26 17:17   ` Tom Rini
2016-02-26 17:31     ` Simon Glass
2016-02-26  4:00 ` [U-Boot] [PATCH 9/9] Drop various features when the command line is not available Simon Glass
2016-02-26 17:17   ` Tom Rini
2016-02-29 23:47   ` Stephen Warren [this message]
2016-02-29 23:56     ` Tom Rini
2016-03-03  0:25       ` Simon Glass
2016-03-03  0:58         ` 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=56D4D887.2000303@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.