linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Riley Williams <rhw@MemAlpha.CX>,
	Adrian Cox <adrian@humboldt.co.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Probable endianess problem in TLAN driver
Date: Sat, 9 Jun 2001 23:45:34 -0700 (PDT)	[thread overview]
Message-ID: <15139.6030.237198.508845@pizda.ninka.net> (raw)
In-Reply-To: <26927.992129768@redhat.com>
In-Reply-To: <15138.44403.815959.756121@pizda.ninka.net> <15138.42357.146305.892652@pizda.ninka.net> <Pine.LNX.4.33.0106092356360.23184-100000@infradead.org> <26927.992129768@redhat.com>


David Woodhouse writes:
 > davem@redhat.com said:
 > > Riley Williams writes:
 > >  > Even if that wasn't true, aren't the above all self-recursive
 > >  > definitions that would prevent anything calling them from compiling?
 > 
 > > Yes, it looks that way. 
 > 
 > cpp doesn't recurse. 

My bad.  What I actually mean is that it simply wouldn't work.
They'd have to do something like drivers/net/eepro100.c does
(grep for "#ifndef USE_IO").

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-06-10  6:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09  4:35 Probable endianess problem in TLAN driver Paulo Afonso Graner Fessel
2001-06-09 10:23 ` Adrian Cox
2001-06-09 22:38 ` David S. Miller
2001-06-09 22:58   ` Riley Williams
2001-06-09 23:36     ` David Woodhouse
2001-06-10  6:45     ` David S. Miller [this message]
2001-06-09 23:12   ` David S. Miller
2001-06-09 10:11 Mathiasen, Torben
2001-06-09 16:21 ` Paulo Afonso Graner Fessel

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=15139.6030.237198.508845@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=adrian@humboldt.co.uk \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhw@MemAlpha.CX \
    /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;
as well as URLs for NNTP newsgroup(s).