From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: andy@greyhouse.net, netdev@vger.kernel.org, lhh@redhat.com,
fubar@us.ibm.com, bonding-devel@lists.sourceforge.net
Subject: Re: [net-2.6 PATCH] bonding: fix broken multicast with round-robin mode
Date: Wed, 31 Mar 2010 14:00:55 -0700 (PDT) [thread overview]
Message-ID: <20100331.140055.246389406.davem@davemloft.net> (raw)
In-Reply-To: <1270048448.2103.28.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 31 Mar 2010 17:14:08 +0200
> ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux- make vmlinux
>
> so, it was a cross compiler :
>
> /data/x86-64/bin/x86_64-unknown-linux-gcc-4.1.2 -v
> Using built-in specs.
> Target: x86_64-unknown-linux
> Configured with: ../gcc-4.1.2/configure --prefix=/data/x86-64
> --target=x86_64-unknown-linux --enable-languages=c --disable-shared
> --disable-multilib --disable-threads --disable-libssp --without-headers
> --disable-libmudflap
> Thread model: single
> gcc version 4.1.2
Funny how going back in time gives us better diagnostic messages from
the compiler :-)
FWIW I also didn't get the warning, and that was with gcc-4.5 built
from the gcc trunk just the other day.
I suspect this is to do with a change to what warnings get enabled by
default with the -W options we put in the cflags rather than gcc
losing the ability to detect this case.
next prev parent reply other threads:[~2010-03-31 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 21:40 [net-2.6 PATCH] bonding: fix broken multicast with round-robin mode Andy Gospodarek
2010-03-25 22:31 ` Jay Vosburgh
2010-03-26 0:49 ` [net-2.6 PATCH v2] " Andy Gospodarek
2010-03-26 0:55 ` Jay Vosburgh
2010-03-31 9:08 ` [net-2.6 PATCH] " Eric Dumazet
2010-03-31 14:49 ` Andy Gospodarek
2010-03-31 15:14 ` Eric Dumazet
2010-03-31 21:00 ` David Miller [this message]
2010-03-31 21:23 ` Eric Dumazet
2010-03-31 21:25 ` 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=20100331.140055.246389406.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=lhh@redhat.com \
--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.