All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: tipc-discussion@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: tipc on sparc32
Date: Tue, 02 Sep 2008 23:26:27 -0700 (PDT)	[thread overview]
Message-ID: <20080902.232627.209816179.davem@davemloft.net> (raw)
In-Reply-To: <20080902.231201.184658566.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Tue, 02 Sep 2008 23:12:01 -0700 (PDT)

> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Tue, 2 Sep 2008 22:40:59 -0700
> 
> > sparc32 allmodconfig:
> > 
> > In file included from net/tipc/link.h:43,
> >                  from net/tipc/bcast.c:41:
> > net/tipc/node.h:71: error: redefinition of 'struct node'
> > 
> > sparc32 likes catching code which uses insufficiently cautiously chosen
> > identifiers.  dlm is presently blowing up on sparc32 because it has a
> > to_node() function.
> > 
> > Arguably, sparc32 should be fixed, but I'd suggest that random bits of
> > networking code should not be using identifiers as generic-sounding as "node".
> 
> I'll fix sparc for the time being, thanks.

Actually, the conflict is between the include/linux/node.h which the
generic device layer uses, and TIPC.

This isn't a sparc specific problem.

And the DLM issue is the same thing.

It might be triggering on sparc32 because linux/node.h gets included
in the tangle of arch and non-arch include files that happen during
the build, but that's benign as far as blaming sparc is concerned.

I can take care of TIPC.

Andrew can you take a stab at DLM?

Thanks.

  reply	other threads:[~2008-09-03  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03  5:40 tipc on sparc32 Andrew Morton
2008-09-03  6:12 ` David Miller
2008-09-03  6:26   ` David Miller [this message]
2008-09-03  6:40     ` David Miller
2008-09-03  6:54       ` Andrew Morton
2008-09-03  6:46     ` Andrew Morton
2008-09-03  6:47       ` David Miller

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=20080902.232627.209816179.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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.