From: Guenter Roeck <linux@roeck-us.net>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: stable <stable@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: Build failures in v3.18-stable-queue (x86, s390)
Date: Thu, 14 Apr 2016 07:52:56 -0700 [thread overview]
Message-ID: <570FAEC8.9040605@roeck-us.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1604141558220.1604@schleppi>
On 04/14/2016 07:03 AM, Sebastian Ott wrote:
> On Thu, 14 Apr 2016, Guenter Roeck wrote:
>> s390:allmodconfig:
>>
>> arch/s390/pci/pci.c: In function 'pci_base_init':
>> arch/s390/pci/pci.c:843:2: error: call to '__compiletime_assert_844' declared
>> with attribute error:
>> BUILD_BUG_ON failed: !is_power_of_2(__alignof__(struct zpci_fmb)) ||
>> __alignof__(struct zpci_fmb) < sizeof(struct zpci_fmb)
>>
>> Bisected to commit "s390/pci: enforce fmb page boundary rule".
>
> Do you have a pointer to a git tree or to the 3.18 version of that patch.
> I don't see how that BUILD_BUG_ON should be triggered since both the size
> and alignment of this structure are 64 bytes.
>
Try git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git,
branch stable-queue-import-3.18. git describe should report v3.18.30-167-gfcc3f16
for the tip of the branch (at least that is what my builder picked up).
Thanks,
Guenter
next prev parent reply other threads:[~2016-04-14 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:44 Build failures in v3.18-stable-queue (x86, s390) Guenter Roeck
2016-04-14 14:03 ` Sebastian Ott
2016-04-14 14:52 ` Guenter Roeck [this message]
2016-04-14 20:49 ` Sebastian Ott
2016-04-15 2:58 ` Sasha Levin
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=570FAEC8.9040605@roeck-us.net \
--to=linux@roeck-us.net \
--cc=matt.fleming@intel.com \
--cc=sasha.levin@oracle.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=stable@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).