All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: bridge@lists.linux-foundation.org, linus.luessing@web.de,
	davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [Bridge] build breakage due to br_multicast.c referencing ipv6_dev_get_saddr()
Date: Wed, 16 Mar 2011 08:24:41 -0700	[thread overview]
Message-ID: <20110316082441.45db3018@nehalam> (raw)
In-Reply-To: <4D80BC5B0200007800036D85@vpn.id2.novell.com>

On Wed, 16 Mar 2011 12:34:19 +0000
"Jan Beulich" <JBeulich@novell.com> wrote:

> With BRIDGE=y and IPV6=m commit
> fe29ec41aaa51902aebd63658dfb04fe6fea8be5 ("bridge: Use IPv6
> link-local address for multicast listener queries") causes the build to
> break.

Rather than continue with the config games, lets just make the necessary
ipv6 pieces accessible.

-- 

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: <linus.luessing@web.de>, <davem@davemloft.net>,
	<bridge@lists.linux-foundation.org>, <netdev@vger.kernel.org>
Subject: Re: build breakage due to br_multicast.c referencing ipv6_dev_get_saddr()
Date: Wed, 16 Mar 2011 08:24:41 -0700	[thread overview]
Message-ID: <20110316082441.45db3018@nehalam> (raw)
In-Reply-To: <4D80BC5B0200007800036D85@vpn.id2.novell.com>

On Wed, 16 Mar 2011 12:34:19 +0000
"Jan Beulich" <JBeulich@novell.com> wrote:

> With BRIDGE=y and IPV6=m commit
> fe29ec41aaa51902aebd63658dfb04fe6fea8be5 ("bridge: Use IPv6
> link-local address for multicast listener queries") causes the build to
> break.

Rather than continue with the config games, lets just make the necessary
ipv6 pieces accessible.

-- 

  reply	other threads:[~2011-03-16 15:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 12:34 [Bridge] build breakage due to br_multicast.c referencing ipv6_dev_get_saddr() Jan Beulich
2011-03-16 12:34 ` Jan Beulich
2011-03-16 15:24 ` Stephen Hemminger [this message]
2011-03-16 15:24   ` Stephen Hemminger
2011-03-16 17:49   ` [Bridge] " David Miller
2011-03-16 17:49     ` David Miller
2011-03-17  7:53     ` [Bridge] " Jan Beulich
2011-03-17  7:53       ` Jan Beulich
2011-03-17  8:01   ` [Bridge] " Jan Beulich
2011-03-17  8:01     ` Jan Beulich
2011-03-17  8:23     ` [Bridge] " Eric Dumazet
2011-03-17  8:23       ` Eric Dumazet
2011-03-17 13:00     ` [Bridge] " David Miller
2011-03-17 13:00       ` David Miller
2011-03-16 16:41 ` [Bridge] " Stephen Hemminger
2011-03-16 16:41   ` Stephen Hemminger
2011-03-16 17:34 ` [Bridge] " Brian Haley
2011-03-16 17:34   ` Brian Haley
2011-03-17  7:57   ` [Bridge] " Jan Beulich
2011-03-17  7:57     ` Jan Beulich
2011-03-17 13:45     ` [Bridge] " Brian Haley
2011-03-17 13:45       ` Brian Haley
2011-03-16 17:49 ` [Bridge] " David Miller
2011-03-16 17:49   ` David Miller
2011-03-22 21:40 ` [Bridge] " Linus Lüssing
2011-03-22 21:40   ` Linus Lüssing
2011-03-22 21:40   ` [Bridge] [PATCH] bridge: Fix possibly wrong MLD queries' ethernet source address Linus Lüssing
2011-03-22 21:40     ` Linus Lüssing
2011-03-23  2:26     ` [Bridge] " David Miller
2011-03-23  2:26       ` 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=20110316082441.45db3018@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=JBeulich@novell.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linus.luessing@web.de \
    --cc=netdev@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.