From: "Alon Bar-Lev" <alon.barlev@gmail.com>
To: "Paul Mundt" <lethal@linux-sh.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "Andi Kleen" <ak@suse.de>,
"Matt Domsch" <Matt_Domsch@dell.com>,
"Andrew Morton" <akpm@osdl.org>,
linux-kernel@vger.kernel.org, johninsd@san.rr.com,
davej@codemonkey.org.uk, trini@kernel.crashing.org,
davem@davemloft.net, ecd@brainaid.de, wli@holomorphy.com,
rc@rc0.org.uk, spyro@f2s.com, rth@twiddle.net,
ralf@linux-mips.org, matthew@wil.cx, grundler@parisc-linux.org,
geert@linux-m68k.org, zippel@linux-m68k.org,
heiko.carstens@de.ibm.com, uclinux-v850@lsi.nec.co.jp,
chris@zankel.net
Subject: Re: [PATCH 19/26] Dynamic kernel command-line - sh
Date: Thu, 12 Oct 2006 10:30:59 +0200 [thread overview]
Message-ID: <9e0cf0bf0610120130y5656e99fgf0bb9305d1467b6e@mail.gmail.com> (raw)
In-Reply-To: <20061012081613.GA8559@linux-sh.org>
On 10/12/06, Paul Mundt <lethal@linux-sh.org> wrote:
> The sh bits look fine, though I'm fairly impartial to this change. It
> doesn't seem like this is going to be needed in very many places..
Thank you for your quick response!
But I failed to push i386 command-line size to more than 256 bytes...
You are right, it is required only for memory extreme devices...
Options:
1. Add COMMAND_LINE_SIZE to kernel config - was rejected because
kernel has already too much parameters, this was the initial patch
more than a year ago.
2. Just increase COMMAND_LINE_SIZE of i386, x86_64 - was rejected
because of it affecting low memory devices.
3. Convert the command-line into dynamically allocated buffers - this try.
> In the future, you may also wish to CC linux-arch if you want the
> attention of architecture maintainers.
Thank you, I was not aware of this.
I hope there will be no take 3 :)
Best Regards,
Alon Bar-Lev.
next prev parent reply other threads:[~2006-10-12 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610112111.02040.alon.barlev@gmail.com>
[not found] ` <200610112117.10698.alon.barlev@gmail.com>
[not found] ` <200610112116.56120.alon.barlev@gmail.com>
2006-10-12 8:16 ` Paul Mundt
2006-10-12 8:30 ` Alon Bar-Lev [this message]
2007-01-18 12:58 [patch 00/26] Dynamic kernel command-line Bernhard Walle
2007-01-18 12:59 ` [patch 19/26] Dynamic kernel command-line - sh Bernhard Walle
-- strict thread matches above, loose matches on Subject: below --
2006-12-02 10:47 [PATCH 00/26] Dynamic kernel command-line Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-09-03 22:15 [PATCH 00/26] Dynamic kernel command-line - Resend please ignore last Alon Bar-Lev
2006-09-03 22:22 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-09-03 21:50 [PATCH 00/26] Dynamic kernel command-line Alon Bar-Lev
2006-09-03 22:01 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
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=9e0cf0bf0610120130y5656e99fgf0bb9305d1467b6e@mail.gmail.com \
--to=alon.barlev@gmail.com \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chris@zankel.net \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=ecd@brainaid.de \
--cc=geert@linux-m68k.org \
--cc=grundler@parisc-linux.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=johninsd@san.rr.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=ralf@linux-mips.org \
--cc=rc@rc0.org.uk \
--cc=rth@twiddle.net \
--cc=spyro@f2s.com \
--cc=trini@kernel.crashing.org \
--cc=uclinux-v850@lsi.nec.co.jp \
--cc=wli@holomorphy.com \
--cc=zippel@linux-m68k.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®