From: William Heimbigner <icxcnika@mar.tar.cc>
To: linux-kernel@vger.kernel.org
Subject: Question re config_cmdline
Date: Thu, 26 Apr 2007 22:56:54 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704262255170.25153@server.thyself> (raw)
I noticed that many of the architectures have support for CONFIG_CMDLINE (which
allows for the configuration of a default kernel command lines), however, x86
doesn't. Is this intentional, and if so, why? It seems to me that a built in
command line would be architecture-independent.
William Heimbigner
icxcnika@mar.tar.cc
reply other threads:[~2007-04-26 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0704262255170.25153@server.thyself \
--to=icxcnika@mar.tar.cc \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®