All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Florian Bomers <Florian.Bomers@Sun.COM>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Compilation warnings on amd64
Date: Tue, 08 Jun 2004 18:11:08 +0200	[thread overview]
Message-ID: <s5hacze2foj.wl@alsa2.suse.de> (raw)
In-Reply-To: <40C5D62F.4060609@sun.com>

At Tue, 08 Jun 2004 08:07:27 -0700,
Florian Bomers wrote:
> 
> Hi,
> 
> I updated an opteron system from SLES 8.1 to 8.1 patchlevel 3, kernel 
> 2.4.21-127-default, and I get the warnings below for almost every file 
> to be compiled. It seems to work fine though.

this should be harmless.  it happens on old SUSE kernels sometimes
because it includes the ALSA modules.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org

      reply	other threads:[~2004-06-08 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 15:07 Compilation warnings on amd64 Florian Bomers
2004-06-08 16:11 ` Takashi Iwai [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=s5hacze2foj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Florian.Bomers@Sun.COM \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.