All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: dank@trellisinc.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pcnet32 compilation fix for 2.4.3pre6
Date: Thu, 29 Mar 2001 15:29:04 -0600	[thread overview]
Message-ID: <3AC3A920.835C9550@inet.com> (raw)
In-Reply-To: <20010329210925.3161C6E099@fancypants.trellisinc.com> <m3hf0cs1xu.fsf@otr.mynet.cygnus.com>

Ulrich Drepper wrote:
> 
> dank@trellisinc.com writes:
> 
> > with the new ansi standard, this use of __inline__ is no longer
> > necessary,
> 
> This is not correct.  Since the semantics of inline in C99 and gcc
> differ all code which depends on the gcc semantics should continue to
> use __inline__ since this keyword will hopefully forever signal the
> gcc semantics.

So what are the differences?  (Or, what would I read to learn the
differences?)
When are they important to us?

TIA,

Eli
-----------------------.           Rule of Accuracy: When working toward
Eli Carter             |            the solution of a problem, it always 
eli.carter(at)inet.com `------------------ helps if you know the answer.

  reply	other threads:[~2001-03-29 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22  6:38 [PATCH] pcnet32 compilation fix for 2.4.3pre6 Andrzej Krzysztofowicz
2001-03-22 10:43 ` Jeff Garzik
2001-03-22 13:40 ` Jeff Garzik
2001-03-22 14:39   ` Eli Carter
2001-03-22 14:46     ` Jeff Garzik
2001-03-22 15:10       ` Eli Carter
2001-03-22 16:23         ` Jeff Garzik
2001-03-29 21:09         ` dank
2001-03-29 21:25           ` Ulrich Drepper
2001-03-29 21:29             ` Eli Carter [this message]
2001-03-29 22:55             ` Tom Leete
2001-03-30  9:36               ` Jeff Garzik
2001-03-22 14:49   ` Alan Cox

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=3AC3A920.835C9550@inet.com \
    --to=eli.carter@inet.com \
    --cc=dank@trellisinc.com \
    --cc=drepper@cygnus.com \
    --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.