All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.2-rc3-tiny1 for small systems
Date: Mon, 2 Feb 2004 21:50:01 +0100	[thread overview]
Message-ID: <20040202205001.GA4443@fs.tum.de> (raw)
In-Reply-To: <20040202192905.GA21888@waste.org>

On Mon, Feb 02, 2004 at 01:29:05PM -0600, Matt Mackall wrote:
> On Mon, Feb 02, 2004 at 07:39:44PM +0100, Adrian Bunk wrote:
> > On Sat, Jan 31, 2004 at 11:23:48PM -0600, Matt Mackall wrote:
> > >...
> > 
> > The patch contains 3 .orig files that could be removed:
> > linux-2.6.2-rc3/arch/i386/boot/compressed/misc.c.orig
> > linux-2.6.2-rc3/arch/i386/mm/init.c.orig
> > linux-2.6.2-rc3/fs/proc/proc_misc.c.orig
> > 
> > > Latest release includes:
> > >...
> > >  - enhanced CPU feature selection (Adrian Bunk)
> > >...
> > 
> > You could kill all the CPU_SUP_* options with my CPU selection scheme.
> 
> I looked at that but ended up deciding I still didn't have the desired
> granularity. So I'm currently thinkg of your stuff as "select family"
> and my stuff as "select vendor support".

Note that this only makes a difference for the CPU_486 and CPU_586 
choices - all more recent CPU_* options include both.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2004-02-02 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01  5:23 2.6.2-rc3-tiny1 for small systems Matt Mackall
2004-02-02 18:39 ` Adrian Bunk
2004-02-02 19:29   ` Matt Mackall
2004-02-02 20:50     ` Adrian Bunk [this message]

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=20040202205001.GA4443@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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 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.