public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Me <bodnar42@bodnar42.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] include/linux/coda.h
Date: Mon, 21 May 2001 21:24:20 -0700	[thread overview]
Message-ID: <01052121242000.31459@bodnar42.dhs.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 174 bytes --]

 Coda.h assumes that __KERNEL__ can only be defined if __linux__ is, which is 
painfully false. This allows the kernel compile to get farther on my token 
FreeBSD box.

-Ryan

[-- Attachment #2: crosscompile.diff --]
[-- Type: text/x-c, Size: 516 bytes --]

--- linux/include/linux/coda.h	Wed Apr 25 16:18:54 2001
+++ linux/include/linux/coda.h	Mon May 21 21:19:21 2001
@@ -100,6 +100,10 @@
 
 #if defined(__linux__)
 #define cdev_t u_quad_t
+#else
+#define cdev_t dev_t
+#endif
+
 #ifndef __KERNEL__
 #if !defined(_UQUAD_T_) && (!defined(__GLIBC__) || __GLIBC__ < 2)
 #define _UQUAD_T_ 1
@@ -108,9 +112,6 @@
 #else /*__KERNEL__ */
 typedef unsigned long long u_quad_t;
 #endif /* __KERNEL__ */
-#else
-#define cdev_t dev_t
-#endif
 
 #ifdef __CYGWIN32__
 struct timespec {

             reply	other threads:[~2001-05-22  4:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  4:24 Me [this message]
2001-05-22 13:18 ` [PATCH] include/linux/coda.h Jan Harkes
2001-05-22 14:21   ` Me
2001-05-22 14:34     ` Alan Cox
2001-05-22 15:57       ` David Woodhouse
2001-05-22 16:22         ` Jan Harkes
2001-05-22 16:40       ` Ryan Cumming
2001-05-22 16:56         ` UML cross-platform build problems (was Re: [PATCH] include/linux/coda.h) Jan Harkes
2001-05-22 20:13           ` Jeff Dike
2001-05-22 18:06         ` [PATCH] include/linux/coda.h Alan Cox
2001-05-24 17:33         ` Thomas Dodd

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=01052121242000.31459@bodnar42.dhs.org \
    --to=bodnar42@bodnar42.dhs.org \
    --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