From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Mon, 29 Feb 2016 16:47:19 -0700
Subject: [U-Boot] [PATCH 9/9] Drop various features when the command
 line is not available
In-Reply-To: <1456459256-32643-10-git-send-email-sjg@chromium.org>
References: <1456459256-32643-1-git-send-email-sjg@chromium.org>
 <1456459256-32643-10-git-send-email-sjg@chromium.org>
Message-ID: <56D4D887.2000303@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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?