All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Momchil Velikov <velco@fadata.bg>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __linux__ and cross-compile
Date: Sun, 20 Jan 2002 16:37:24 +0000	[thread overview]
Message-ID: <2960.1011544644@redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0201201719060.20948-100000@mimas.fachschaften.tu-muenchen.de>
In-Reply-To: <Pine.NEB.4.44.0201201719060.20948-100000@mimas.fachschaften.tu-muenchen.de>


bunk@fs.tum.de said:
>  It's clear that code that is part of an "#ifndef __linux__" will
> never be included on any other OS than Linux.

True. But unfortunately that's not a useful guarantee. This code doesn't
(normally) run _on_ Linux. It is _in_ Linux, and it's still possible that
the offending code won't get included when it should.

> Is this also garuanteed for "#ifndef __KERNEL__"? 

We think *BSD uses _KERNEL, and don't know of anything else which defines 
__KERNEL__ other than Linux. So he's switching from something that's known 
broken to something which we _believe_ will be reliable.

--
dwmw2



  reply	other threads:[~2002-01-20 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20 13:59 [PATCH] __linux__ and cross-compile Momchil Velikov
2002-01-20 14:23 ` Adrian Bunk
2002-01-20 15:08   ` Momchil Velikov
2002-01-20 15:17     ` Adrian Bunk
2002-01-20 16:04       ` Momchil Velikov
2002-01-20 16:15       ` David Woodhouse
2002-01-20 16:29         ` Adrian Bunk
2002-01-20 16:37           ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  7:43 Zwane Mwaikambo

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=2960.1011544644@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=velco@fadata.bg \
    /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.