public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: ak@suse.de, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>,
	discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: let x86_64 no longer define X86
Date: Fri, 19 Nov 2004 02:19:08 +0100	[thread overview]
Message-ID: <20041119011908.GB6589@stusta.de> (raw)
In-Reply-To: <419D48DE.6030703@yahoo.com.au>

On Fri, Nov 19, 2004 at 12:14:06PM +1100, Nick Piggin wrote:
> Adrian Bunk wrote:
> 
> >And if you want to support both older and more recent kernels, the 
> >following dependencies will be correct both before and after this 
> >change:
> >- (X86 && !X86_64)
> >- (X86 && X86_64)
> >
> 
> This last one surely can't be correct before *and* afterwards. But even in
> the current system, it is a pretty perverse thing to check for. I guess you
> meant:
> 
> (X86 || X86_64)

Yes, thanks for the correcting my typo.

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-11-19  1:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19  0:51 RFC: let x86_64 no longer define X86 Adrian Bunk
2004-11-19  1:14 ` Nick Piggin
2004-11-19  1:19   ` Adrian Bunk [this message]
2004-11-19  1:31 ` [discuss] " Paul Menage
2004-11-19 12:28   ` Adrian Bunk
2004-11-19 12:40     ` Andi Kleen
2004-11-19 13:29       ` Adrian Bunk
2004-11-19  8:51 ` Andi Kleen
2004-11-19 10:21   ` Jeff Garzik
2004-11-19 10:34     ` [discuss] " Andi Kleen
2004-11-19 11:28       ` David Woodhouse
2004-11-19 11:55         ` Andi Kleen
2004-11-19 11:50           ` David Woodhouse
2004-11-19 12:05             ` Andi Kleen
2004-11-19 12:12               ` Jeff Garzik
2004-11-19 12:19                 ` Andi Kleen
2004-11-19 12:37                   ` Jeff Garzik
2004-11-19 12:45                     ` Adrian Bunk
2004-11-19 12:55                     ` linux-os
2004-11-19 13:04                       ` Jeff Garzik
2004-11-19 13:35                         ` Raul Miller
2004-11-19 14:11                   ` Adrian Bunk
2004-11-19 13:58               ` David Woodhouse
2004-11-19 12:05       ` Adrian Bunk
2004-11-19 12:09         ` Andi Kleen
2004-11-19 11:18 ` Takashi Iwai
2004-11-19 22:31   ` Paul Mackerras

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=20041119011908.GB6589@stusta.de \
    --to=bunk@stusta.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=torvalds@osdl.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