From: Coywolf Qi Hunt <coywolf@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, lkml@dodo.com.au, Arjan van de Ven <arjan@infradead.org>
Subject: Re: transmeta-no-procfs-build-fix.patch added to -mm tree
Date: Thu, 17 Nov 2005 19:51:28 +0800 [thread overview]
Message-ID: <2cd57c900511170351g5f2e593bw@mail.gmail.com> (raw)
In-Reply-To: <200508020322.j723MwfR023586@shell0.pdx.osdl.net>
2005/8/2, akpm@osdl.org <akpm@osdl.org>:
>
> The patch titled
>
> transmeta: CONFIG_PROC_FS=n build fix
>
> has been added to the -mm tree. Its filename is
>
> transmeta-no-procfs-build-fix.patch
> From: Andrew Morton <akpm@osdl.org>
>
> Fix bug found by Grant Coady <lkml@dodo.com.au>'s autobuild setup.
>
>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> arch/i386/kernel/cpu/transmeta.c | 2 ++
> 1 files changed, 2 insertions(+)
>
> diff -puN arch/i386/kernel/cpu/transmeta.c~transmeta-no-procfs-build-fix arch/i386/kernel/cpu/transmeta.c
> --- devel/arch/i386/kernel/cpu/transmeta.c~transmeta-no-procfs-build-fix 2005-08-01 20:15:42.000000000 -0700
> +++ devel-akpm/arch/i386/kernel/cpu/transmeta.c 2005-08-01 20:16:14.000000000 -0700
> @@ -77,9 +77,11 @@ static void __init init_transmeta(struct
> if ( c->x86 == 5 && (c->x86_capability[0] & USER686) == USER686 )
> c->x86 = 6;
>
> +#ifdef CONFIG_SYSCTL
> /* randomize_va_space slows us down enormously;
> it probably triggers retranslation of x86->native bytecode */
> randomize_va_space = 0;
> +#endif
> }
You haven't fixed the problem. It would fall back to
#define randomize_va_space 1
>
> static void transmeta_identify(struct cpuinfo_x86 * c)
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
parent reply other threads:[~2005-11-17 11:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200508020322.j723MwfR023586@shell0.pdx.osdl.net>]
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=2cd57c900511170351g5f2e593bw@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dodo.com.au \
/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.