All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: bunk@fs.tum.de, marcelo.tosatti@cyclades.com, netdev@oss.sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.26-pre1: SCTP compile error
Date: Thu, 26 Feb 2004 22:49:58 -0800	[thread overview]
Message-ID: <20040226224958.24eb29fb.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402261533500.19577@localhost.localdomain>

On Thu, 26 Feb 2004 15:53:58 -0800 (PST)
Sridhar Samudrala <sri@us.ibm.com> wrote:

> I missed this warning as i don't have irda enabled in my config.
> A simple fix would be to rename the macro in sctp.h to
> SCTP_MSECS_TO_JIFFIES.

I've fixed this in my tree.

> > ipv6.c: In function `sctp_v6_xmit':
> > ipv6.c:189: request for member `in6_u' in something not a structure or union
> > ipv6.c:189: request for member `in6_u' in something not a structure or union
> 
> I am not seeing these errors with either gcc3.2.2 or gcc2.96. But, looking at the
> code, this definitely seems to be a problem. Not sure why the newer versions of
> gcc didn't catch them.

It's trying to use NIP6() on an object that is not a struct in6_addr.
I'll just comment this thing out for now.

      parent reply	other threads:[~2004-02-27  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 19:09 Linux 2.4.26-pre1 Marcelo Tosatti
2004-02-26  0:06 ` [patch] 2.4.26-pre1 - drivers/net/r8169.c Francois Romieu
2004-02-26  6:19   ` Jeff Garzik
2004-02-26 21:27 ` 2.4.26-pre1: SCTP compile error Adrian Bunk
2004-02-26 23:53   ` Sridhar Samudrala
2004-02-27  1:41     ` Sridhar Samudrala
2004-02-27  6:49     ` David S. Miller [this message]

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=20040226224958.24eb29fb.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=netdev@oss.sgi.com \
    --cc=sri@us.ibm.com \
    /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.