From: Chris Snook <csnook@redhat.com>
To: Shen Feng <shen@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why 2 Kernel command line and module option parsers
Date: Tue, 15 Apr 2008 17:02:20 -0400 [thread overview]
Message-ID: <480517DC.3060303@redhat.com> (raw)
In-Reply-To: <48045829.1090609@cn.fujitsu.com>
Shen Feng wrote:
> Hello,
>
> Now we get two Kernel command line and module option parsers, i.e.
> lib/cmdline.c
> lib/parser.c
>
> I think we'd better merge them into one and make a kernel option standard since
> the kernel options become more and more.
Are you volunteering?
next prev parent reply other threads:[~2008-04-15 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 7:24 why 2 Kernel command line and module option parsers Shen Feng
2008-04-15 21:02 ` Chris Snook [this message]
2008-04-16 2:39 ` Shen Feng
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=480517DC.3060303@redhat.com \
--to=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shen@cn.fujitsu.com \
/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