public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: Len Brown <len.brown@intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: Linux 2.4.26-rc1 (cmpxchg vs 80386 build)
Date: Tue, 30 Mar 2004 22:25:33 +0200	[thread overview]
Message-ID: <200403302225.33966.arekm@pld-linux.org> (raw)
In-Reply-To: <1080677134.980.166.camel@dhcppc4>

Dnia Tuesday 30 of March 2004 22:05, Len Brown napisał:
> I can make sure that ACPI checks implicitly or explicitly
> that CMPXCHG is available -- but I can't make sure that
> some other random part of the kernel which may not have
> been written yet does.  So I'd rather that they not build,
> like ACPI didn't.
Well, I asked for this because there is similar case with some DRI drivers in 
kernel. These drivers use cmpxchg and some time ago it was not possible to 
build them for i386 (and of course run on 486+). This AFAIK did not change.

These not yet written parts of kernel do not exist so nothing to worry about 
right now. Anyway there always could be #warning for i386 - easy to catch 
while compiling and would allow to fix that future kernel code then.

> cheers,
> -Len

> > Wouldn't be better to just remove #ifdef CONFIG_X86_CMPXCHG around
> > __cmpxchg() and cmpxchg macro in ./include/asm-i386/system.h so cmpxchg()
> > would be there always even on i386 but leave CONFIG_X86_CMPXCHG macro if
> > anyone want's to check for it in some code. No code duplication and you
> > get what you need.

-- 
Arkadiusz Miśkiewicz     CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

  reply	other threads:[~2004-03-30 20:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615F6939@hdsmsx402.hd.intel.com>
2004-03-29  4:49 ` Linux 2.4.26-rc1 (cmpxchg vs 80386 build) Len Brown
2004-03-29  0:09   ` [ACPI] " Andi Kleen
2004-03-29  5:22   ` Willy Tarreau
2004-03-29  7:01     ` Denis Vlasenko
2004-03-29 19:57       ` Willy Tarreau
2004-03-29 22:07     ` Len Brown
2004-03-30 12:56       ` [ACPI] " Alan Cox
2004-03-30 13:15         ` Richard B. Johnson
2004-03-30 14:22           ` Willy Tarreau
2004-03-30 14:48             ` Richard B. Johnson
2004-03-30 15:09               ` Willy Tarreau
2004-03-30 15:33                 ` Richard B. Johnson
2004-03-30 16:14                   ` Willy Tarreau
2004-03-30 16:42                     ` Chris Friesen
2004-03-30 17:44                       ` Len Brown
2004-03-30 18:30                         ` Arkadiusz Miskiewicz
2004-03-30 20:05                           ` Len Brown
2004-03-30 20:25                             ` Arkadiusz Miskiewicz [this message]
2004-03-30 21:49                               ` Len Brown
2004-03-30 20:08                         ` Bill Davidsen
2004-03-31 11:13                           ` Maciej W. Rozycki
2004-03-31 13:04                             ` Bill Davidsen
2004-03-31 15:02                             ` Jamie Lokier
2004-04-01 12:29                               ` Maciej W. Rozycki
2004-04-01 13:17                                 ` Richard B. Johnson
2004-05-08 10:18                                   ` Denis Vlasenko
2004-04-01 20:46                                 ` Len Brown
2004-04-02 10:54                                   ` Maciej W. Rozycki

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=200403302225.33966.arekm@pld-linux.org \
    --to=arekm@pld-linux.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.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