From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Gerst <brgerst@gmail.com>
Subject: linux-next: build failure after merge of the percpu tree
Date: Fri, 10 Sep 2010 12:45:43 +1000 [thread overview]
Message-ID: <20100910124543.3e8604fd.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hi all,
After merging the percpu tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/vhost/net.c:26:
include/linux/if_macvlan.h: In function 'macvlan_count_rx':
include/linux/if_macvlan.h:69: error: read-only variable 'tcp_ptr__' used as 'asm' output
In file included from drivers/net/macvlan.c:30:
include/linux/if_macvlan.h: In function 'macvlan_count_rx':
include/linux/if_macvlan.h:69: error: read-only variable 'tcp_ptr__' used as 'asm' output
In file included from drivers/net/macvtap.c:2:
include/linux/if_macvlan.h: In function 'macvlan_count_rx':
include/linux/if_macvlan.h:69: error: read-only variable 'tcp_ptr__' used as 'asm' output
Caused by commit 7f56c13698abfb1bdf6cf2b5cfcd80626d44c12e ("x86, percpu:
Optimize this_cpu_ptr").
That line in if_macvlan.h is:
rx_stats = this_cpu_ptr(vlan->rx_stats);
Where vlan is a "const struct macvlan_dev *".
I have used the percpu tree from next-20100909 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-09-10 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 2:45 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-04 4:21 linux-next: build failure after merge of the percpu tree Stephen Rothwell
2011-01-04 5:13 ` Tejun Heo
2011-01-06 4:18 ` Stephen Rothwell
2011-01-06 5:11 ` Tejun Heo
2014-08-27 4:22 Stephen Rothwell
2018-02-26 3:57 Stephen Rothwell
2023-12-11 6:14 Stephen Rothwell
2023-12-11 8:31 ` Alexandre Ghiti
2023-12-11 19:25 ` Dennis Zhou
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=20100910124543.3e8604fd.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brgerst@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tj@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