public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Jonathan Campbell <jon@nerdgrounds.com>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Patches for REALLY TINY 386 kernels
Date: Tue, 17 Jul 2007 14:30:28 -0500	[thread overview]
Message-ID: <20070717193028.GF11166@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707171240040.686@fbirervta.pbzchgretzou.qr>

On Tue, Jul 17, 2007 at 12:59:03PM +0200, Jan Engelhardt wrote:
> 
> On Jul 15 2007 14:00, Jonathan Campbell wrote:
> >
> > These patches were written against the vanilla 2.6.21.1 kernel. They will have
> > no effect UNLESS you make menuconfig and explicitly enable them there.
> >
> >
> inline patches...
> 
> >+config X86_DONT_CPUID
> >+	bool "Disable CPUID support"
> >+	depends on M386 || M486
> 
> I think this should not depend on any model.
> Depend on x86 at best.

Indeed.
 
> 	depends on X86
> 
> >+	default n
> 
> And perhaps it would be helpful to invert it, like the other options, i.e.:
> 
> config X86_CPUID
> 	bool "Enable CPUID support" if X86 && EMBEDDED
> 	default y

Definitely.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-07-17 19:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 21:00 Patches for REALLY TINY 386 kernels Jonathan Campbell
2007-07-15 21:42 ` Nigel Cunningham
2007-07-15 22:45   ` Alan Cox
2007-07-15 23:12     ` Nigel Cunningham
2007-07-15 23:14       ` Satyam Sharma
2007-07-15 23:13         ` Arnd Bergmann
2007-07-15 23:28           ` Satyam Sharma
2007-07-15 23:05 ` Adrian Bunk
2007-07-15 23:08 ` H. Peter Anvin
2007-07-17 10:59 ` Jan Engelhardt
2007-07-17 19:30   ` Matt Mackall [this message]
2007-07-18  2:33 ` Andi Kleen
2007-07-18 15:55   ` H. Peter Anvin
2007-07-18 18:20     ` Andi Kleen
2007-07-18 18:29       ` Jan Engelhardt
2007-07-18 18:38         ` Andi Kleen
2007-07-18 18:45           ` Jan Engelhardt
2007-07-18 18:47             ` Andi Kleen
2007-07-18 20:24         ` John Stoffel
2007-07-18 18:33     ` Adrian Bunk
2007-07-18 18:42       ` Jan Engelhardt
2007-07-18 18:44       ` Andi Kleen
2007-07-18 19:00       ` H. Peter Anvin
2007-07-21 10:09         ` Oleg Verych
2007-07-18 19:41     ` Matt Mackall
2007-07-18 19:50       ` H. Peter Anvin
2007-07-18 20:10       ` Andi Kleen
2007-07-18 20:24         ` H. Peter Anvin
2007-07-18 21:04           ` Andi Kleen
2007-07-18 22:17             ` H. Peter Anvin
2007-07-30 17:59             ` Denis Vlasenko
2007-07-18 20:41         ` Matt Mackall
2007-07-20  7:27           ` Uwe Hermann
2007-07-20  7:35             ` Andi Kleen
2007-07-24 14:49               ` Helge Hafting
2007-07-24 20:50                 ` Yinghai Lu
2007-07-24 22:56                   ` Adrian Bunk
2007-07-25  0:55                     ` Yinghai Lu
2007-07-24 22:45     ` Willy Tarreau
     [not found] <8HjYY-4Jk-15@gated-at.bofh.it>
     [not found] ` <8HlxM-7iT-13@gated-at.bofh.it>
     [not found]   ` <8HlxL-7iT-11@gated-at.bofh.it>
     [not found]     ` <8HlHq-7vR-17@gated-at.bofh.it>
     [not found]       ` <8HlHr-7vR-25@gated-at.bofh.it>
2007-07-16 13:12         ` Bodo Eggert

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=20070717193028.GF11166@waste.org \
    --to=mpm@selenic.com \
    --cc=jengelh@computergmbh.de \
    --cc=jon@nerdgrounds.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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