path: root/com32/elflink/ldlinux/readconfig.c
diff options
authorMatt Fleming <matt.fleming@linux.intel.com>2011-04-06 14:37:43 +0100
committerMatt Fleming <matt.fleming@linux.intel.com>2011-04-16 14:46:37 +0100
commit9d9b677dd1b3bf235c0ee2dd64d476fd9d85db3a (patch)
tree909a6bfa00f9de61a8ead7e12086b4c376e46573 /com32/elflink/ldlinux/readconfig.c
parent8f9153df73881f698c83716283acf5c2bb85029d (diff)
ldlinux: Move cmdline processing out of cli.c
While it makes perfect sense for cli.c to read input from the user and parse certain characters (Ctrl-R, TABs, etc), once that processing is done it should be up to the caller to decide what to do with the expanded cmdline string. For example, the logic to figure out what type of kernel we're loading (calculated from a kernel's filename extension as typed on the command-line) is currently in cli.c, and that is just wrong. That kind of logic belongs in ldlinux.c So move process_command() from cli.c to ldlinux.c and extend it so that if the user types a label name at the prompt, we load the kernel for that label as described in the config file. Now that we've moved all cli history code into edit_cmdline() it seems like a good time to turn it on permanently. Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com>
Diffstat (limited to 'com32/elflink/ldlinux/readconfig.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/com32/elflink/ldlinux/readconfig.c b/com32/elflink/ldlinux/readconfig.c
index 66e84dfb..d78c0151 100644
--- a/com32/elflink/ldlinux/readconfig.c
+++ b/com32/elflink/ldlinux/readconfig.c
@@ -432,7 +432,7 @@ void print_labels(const char *prefix, size_t len)
-static struct menu_entry *find_label(const char *str)
+struct menu_entry *find_label(const char *str)
const char *p;
struct menu_entry *me;