lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070126024411.4d4b6c2e.akpm@osdl.org>
Date:	Fri, 26 Jan 2007 02:44:11 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Tim Bird <tim.bird@...sony.com>
Cc:	Paul Mundt <lethal@...ux-sh.org>,
	linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] init: support preset lpj value as config option

On Thu, 25 Jan 2007 10:24:59 -0800
Tim Bird <tim.bird@...sony.com> wrote:

> Paul Mundt wrote:
> > On Wed, Jan 24, 2007 at 04:12:18PM -0800, Tim Bird wrote:
> >> This patch provides a config option for preset lpj, which means
> >> the value can be easily preserved, and conveyed between developers
> >> in a config file.
> >>
> > This seems excessive, it's already possible to set the preset lpj on the
> > kernel command line, and virtually every one of the embedded
> > architectures supports setting the kernel command line as a config
> > option. Is there any reason why you can't simply set it there as a
> > default instead? It's all going to be .config resident in the end
> > anyways.
> 
> i386 is missing CONFIG_CMDLINE support, and this architecture
> is used in embedded.

So if we add CONFIG_CMDLINE we fix this problem and we bring i386 into line
with other platforms.  It's all good.

>  I think many other x86 derivatives are
> also missing .config-based command line support.  CELF has
> worked to get patches submitted to fix this, but so far these
> haven't been accepted.

You have?

<looks at inbox>

To whom?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ