From: Gabriel C <nix.or.die@googlemail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: net/ipv4/fib_trie.c - compile error (Re: 2.6.23-rc3-mm1)
Date: Wed, 22 Aug 2007 18:32:04 +0200 [thread overview]
Message-ID: <46CC6504.3020500@googlemail.com> (raw)
In-Reply-To: <20070822154111.GI30705@stusta.de>
Adrian Bunk wrote:
> On Wed, Aug 22, 2007 at 05:30:13PM +0200, Gabriel C wrote:
>> Got it with a randconfig ( http://194.231.229.228/kernel/mm/2.6.23-rc3-mm1/r/randconfig-8 )
>>
>> ...
>>
>> net/ipv4/fib_trie.c: In function 'trie_rebalance':
>> net/ipv4/fib_trie.c:969: error: lvalue required as unary '&' operand
>> net/ipv4/fib_trie.c:971: error: lvalue required as unary '&' operand
>> net/ipv4/fib_trie.c:977: error: lvalue required as unary '&' operand
>> net/ipv4/fib_trie.c:980: error: lvalue required as unary '&' operand
>> ...
>
> Side effect of the git-net removal, temporarily removing
> immunize-rcu_dereference-against-crazy-compiler-writers.patch should
> work around it.
Yes it does , thx Adrian
>
> cu
> Adrian
>
Gabriel
next prev parent reply other threads:[~2007-08-22 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070822020648.5ea3a612.akpm@linux-foundation.org>
2007-08-22 15:30 ` net/ipv4/fib_trie.c - compile error (Re: 2.6.23-rc3-mm1) Gabriel C
2007-08-22 15:41 ` Adrian Bunk
2007-08-22 16:32 ` Gabriel C [this message]
2007-08-22 17:03 ` Paul E. McKenney
2007-08-27 6:36 ` Jarek Poplawski
2007-08-27 16:23 ` Paul E. McKenney
[not found] ` <46CC3B27.10604@googlemail.com>
[not found] ` <20070822090953.78a3d90c.akpm@linux-foundation.org>
2007-08-22 17:01 ` 2.6.23-rc3-mm1 Gabriel C
2007-08-22 17:10 ` drivers/net/ppp_generic - __modpost error ( Re: 2.6.23-rc3-mm1 ) Gabriel C
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=46CC6504.3020500@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).