From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] janitor job: CL_SIZE
Date: Thu, 11 Oct 2007 11:45:34 +0000 [thread overview]
Message-ID: <470E0CDE.3090506@bfs.de> (raw)
hi list,
i looked into COMMAND_LINE_SIZE usage and found
./include/asm-mips/bootinfo.h:#define CL_SIZE COMMAND_LINE_SIZE
./include/asm-m68k/setup.h:#define CL_SIZE COMMAND_LINE_SIZE
CL_SIZE is used in:
./arch/ppc/amiga/bootinfo.c:extern char cmd_line[CL_SIZE];
./arch/m68k/mac/config.c:extern char m68k_command_line[CL_SIZE];
./arch/m68k/kernel/setup.c:static char m68k_command_line[CL_SIZE];
./arch/m68k/kernel/setup.c: memcpy(boot_command_line, *cmdline_p, CL_SIZE);
./arch/mips/lasat/prom.c: strncpy(arcs_cmdline, argv[0], CL_SIZE-1);
./arch/mips/lasat/prom.c: arcs_cmdline[CL_SIZE-1] = '\0';
./arch/mips/kernel/setup.c:static char command_line[CL_SIZE];
./arch/mips/kernel/setup.c: char arcs_cmdline[CL_SIZE]=CONFIG_CMDLINE;
./arch/mips/sibyte/cfe/setup.c: if (cfe_getenv("LINUX_CMDLINE", arcs_cmdline, CL_SIZE) < 0) {
./arch/mips/sibyte/cfe/setup.c: arcs_cmdline[CL_SIZE-1] = 0;
./arch/mips/mips-boards/generic/memory.c: char cmdline[CL_SIZE], *ptr;
is there any good reason to do it this way ?
otherwise s/CL_SIZE/COMMAND_LINE_SIZE/ can be used ?
re,
wh
_______________________________________________
REMINDER: this mailing list moved to vger.kernel.org and current one will be discontinued soon.
To resubscribe, send email to majordomo@vger.kernel.org with
"subscribe kernel-janitors" in message body and follow instructions.
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
reply other threads:[~2007-10-11 11:45 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=470E0CDE.3090506@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.