public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Flavio Bruno Leitner <fbl-KCZ47A4bww4P48s/oLjRZg@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: missing cmpxchg on i386.
Date: Tue, 30 Mar 2004 10:15:08 -0300	[thread overview]
Message-ID: <20040330131508.GA3844@conectiva.com.br> (raw)
In-Reply-To: <20040330123735.GD461-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

On Tue, Mar 30, 2004 at 02:37:35PM +0200, Pavel Machek wrote:
> On St 24-03-04 13:23:47, Flavio Bruno Leitner wrote:
> > 
> > Compiling for i386 I got a lot of 
> > include/asm/acpi.h: In function `__acpi_acquire_global_lock`:
> > include/asm/acpi.h:74: warning: implict declaration of function 'cmpxchg' 
> 
> Try compiling for pentium+...

It's impossible, we need to have kernel optimized for i386.
I revert the ChangeSet 1.1557.83.7 until this get fixed.

-- 
Flávio Bruno Leitner <fbl-KCZ47A4bww4P48s/oLjRZg@public.gmane.org>
[ E74B 0BD0 5E05 C385 239E  531C BC17 D670 7FF0 A9E0 ]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-03-30 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 16:23 missing cmpxchg on i386 Flavio Bruno Leitner
     [not found] ` <20040324162347.GA10134-KCZ47A4bww4P48s/oLjRZg@public.gmane.org>
2004-03-30 12:37   ` Pavel Machek
     [not found]     ` <20040330123735.GD461-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-03-30 13:15       ` Flavio Bruno Leitner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-30 14:36 Yu, Luming

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=20040330131508.GA3844@conectiva.com.br \
    --to=fbl-kcz47a4bww4p48s/oljrzg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-AlSwsSmVLrQ@public.gmane.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