From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: linux-mips@linux-mips.org
Cc: anemo@mba.ocn.ne.jp, ralf@linux-mips.org, yoichi_yuasa@tripeaks.co.jp
Subject: [patch 0/6] cleanup setup.c
Date: Tue, 8 Aug 2006 14:48:26 +0200 [thread overview]
Message-ID: <1155041312273-git-send-email-vagabon.xyz@gmail.com> (raw)
Here's a patchset that clean up arch/mips/kernel/setup.c file.
NOTE ! The semantic for initrd command line argument has been
changed mainly because it is now a lot simpler to parse.
Before we were using "rd_start=xxx rd_size=yyy", now the patch uses
"initrd=yyy@xxx". It seems that no default config files use the old
semantic but I'm not sure for bootloader users for example...
Am I allowed to do that ?
Franck
Overall diffstats:
arch/mips/kernel/setup.c | 429 +++++++++++++++++++---------------------------
1 files changed, 177 insertions(+), 252 deletions(-)
next reply other threads:[~2006-08-08 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 12:48 Franck Bui-Huu [this message]
2006-08-08 12:48 ` [PATCH 1/6] setup.c: cleanup bootmem_init() Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 2/6] setup.c: move initrd code inside dedicated functions Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 3/6] setup.c: remove useless includes Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 4/6] setup.c: do not inline functions Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 5/6] setup.c: remove MAXMEM macro Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 6/6] setup.c: use early_param() for early command line parsing Franck Bui-Huu
2006-08-08 12:56 ` Thiemo Seufer
2006-08-08 14:00 ` Franck Bui-Huu
2006-08-08 15:14 ` Thiemo Seufer
2006-08-09 8:15 ` Franck Bui-Huu
2006-08-09 11:12 ` Thiemo Seufer
2006-08-08 16:05 ` Atsushi Nemoto
2006-08-09 8:21 ` Franck Bui-Huu
2006-08-09 14:25 ` Atsushi Nemoto
2006-08-11 7:36 ` Franck Bui-Huu
2006-08-11 14:36 ` Atsushi Nemoto
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=1155041312273-git-send-email-vagabon.xyz@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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