From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-net-drivers@solarflare.com,
Ben Hutchings <bhutchings@solarflare.com>,
Stuart Hodgson <smhodgson@solarflare.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Build regressions/improvements in v3.10-rc1 (s390)
Date: Mon, 13 May 2013 09:41:59 +0200 [thread overview]
Message-ID: <20130513074159.GA4290@osiris> (raw)
In-Reply-To: <alpine.DEB.2.00.1305122250110.5463@ayla.of.borg>
On Sun, May 12, 2013 at 10:50:45PM +0200, Geert Uytterhoeven wrote:
> On Sun, 12 May 2013, Geert Uytterhoeven wrote:
> > However, the full list of errors isn't that unmanageable, so I'm following
> > up with a digested list...
>
> drivers/net/ethernet/sfc/efx.c:646:3: error: call to '__compiletime_assert_648' declared with attribute error: BUILD_BUG_ON failed: sizeof(struct efx_rx_page_state) + EFX_PAGE_IP_ALIGN + EFX_RX_USR_BUF_SIZE > PAGE_SIZE / 2: 2 errors in 2 logs
> v3.10-rc1/s390x/s390-allyesconfig v3.10-rc1/s390x/s390-allmodconfig
that seems to a BUILD_BUG_ON that only triggers on s390, because we have
L1_CACHE_BYTES defined with 256 bytes... which seems to be more than any
other architecture has.
There was a different network driver that had a similar BUILD_BUG_ON, but
it got removed.
Right, it was the igb driver:
http://comments.gmane.org/gmane.linux.network/261378
next parent reply other threads:[~2013-05-13 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1305122130270.3789@ayla.of.borg>
[not found] ` <alpine.DEB.2.00.1305122239040.5463@ayla.of.borg>
[not found] ` <alpine.DEB.2.00.1305122250110.5463@ayla.of.borg>
2013-05-13 7:41 ` Heiko Carstens [this message]
2013-05-13 16:41 ` Build regressions/improvements in v3.10-rc1 (s390) Ben Hutchings
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=20130513074159.GA4290@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=bhutchings@solarflare.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=smhodgson@solarflare.com \
/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).