All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Inconsistent "#ifdef __KERNEL__" on different architectures
Date: Sun, 27 May 2001 21:16:09 +0200	[thread overview]
Message-ID: <3B115279.CE436CEA@alsa-project.org> (raw)
In-Reply-To: <Pine.NEB.4.33.0105271903050.4227-100000@mimas.fachschaften.tu-muenchen.de>

Adrian Bunk wrote:
> 
> Hi,
> 
> while looking for the reason of a build failure of the ALSA libraries on
> ARM [1] I discovered the following strange thing:
> 
> On some architectures a function is inside an "#ifdef __KERNEL__" in the
> header file and on others not. Is there a reason for this or is this
> inconsistency simply a bug?

This is a bug on some architectures, I've personally fixed this on PPC
sending a patch to Cort Dougan. It has been included in 2.4.5.

I'd like you send a patch to maintainers (or perhaps to Alan).

-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

  parent reply	other threads:[~2001-05-27 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 17:25 Inconsistent "#ifdef __KERNEL__" on different architectures Adrian Bunk
2001-05-27 17:29 ` Alan Cox
2001-05-27 19:16 ` Abramo Bagnara [this message]
2001-05-27 21:07   ` Adrian Bunk
2001-05-27 21:42     ` Russell King - ARM Linux
2001-05-27 22:10     ` Philip Blundell
2001-05-29 22:30       ` Ralf Baechle
2001-06-02 20:29         ` Adrian Bunk
2001-06-05  4:09           ` Paul Mackerras
2001-06-05  9:33             ` Adrian Bunk
2001-06-05 12:15               ` Paul Mackerras
2001-06-06  6:51             ` Albert D. Cahalan

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=3B115279.CE436CEA@alsa-project.org \
    --to=abramo@alsa-project.org \
    --cc=bunk@fs.tum.de \
    --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 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.