All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Alexander Graf <agraf@suse.de>, KVM list <kvm@vger.kernel.org>
Subject: Re: 3.7-rc2 build failure on s390x
Date: Tue, 06 Nov 2012 14:20:24 -0500	[thread overview]
Message-ID: <509962F8.7040204@suse.com> (raw)
In-Reply-To: <20121106140203.2a7f5e38@BR9GNB5Z>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/6/12 8:02 AM, Cornelia Huck wrote:
> On Mon, 05 Nov 2012 11:13:42 -0500 Jeff Mahoney <jeffm@suse.com>
> wrote:
> 
>> 
>> It's a different build issue with -rc3 (and now -rc4).
>> 
>> linux-3.7-rc4/include/linux/kvm_para.h:9:2: error: implicit
>> declaration of function 'kvm_arch_para_features'
>> [-Werror=implicit-function-declaration]
>> 
>> Config attached.
>> 
>> -Jeff
>> 
> 
> Plain vanilla 3.7-rc4 builds fine for me with your config and make 
> oldconfig. But from your config I see that you seem to have some 
> patches on top. So my guess would be that you should verify these 
> patches first :)

Yep. Someone on our end added a patch to fix the original issue that
was left in after it was fixed differently upstream.

Sorry for the noise.

- -Jeff

- -- 
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQmWL3AAoJEB57S2MheeWyETEQALv9y0G8PVpIc/152irJd663
RWAYEjTC3PNeRf28hd85l03c+z0qH/MqZXNbc4NdoXhunuRbrARCpXl52eyxQmLs
dM6fvNpJoRRHPCS3j96W7s+EPSXahxJBV6RED+iN9hOntgRG9qiW5q+WLPik5Lpf
FL4j4/qUQZh0Zyqr3L9X7FnTPxITUVJiilaHmVymvUFQBhlVdSVsPpsSrJvaoNrz
cav3ThoW+NHAfyDqQGRJJy4f3hL6zqkQJGgCiH2V7/DaK8LQkxV7L6mWnapH4Xnn
CDdL1x3e4htRREdlQAaN/RqHpvvWGlamLMahA0dY47TbN912oIxSBkfhn09XGxBe
ODcQgl7UUfknhs5M4nwbiTkCZGPiHeRg8FRAg147bmiy2eCwp7pYgOpgQraKtrMO
pfZatfudMXQyC3T/AWsrDXMr4vdYX7WLW78uy3wqjltYSUz5L+5zpqKCAk8kWLm/
G21g4arNV7FWFq/hzl2ceqFPTzFVIsOa6xyh9w5TdHoekzUqsoyvyg6s/vL88XxZ
Jgic3dJ7n25vEAHZR0ruO8CsQy537q1Y+pheCjox0fIfAREQkGNPKABLYonjl6xZ
m21x90S0lMpyhD+6+sMdYN6d3K8JmGcYaURpBAvAyDz442dRsv7kHcxdCAs+hBEe
G2+ewz3gnJvvNXUM8aM4
=Zrok
-----END PGP SIGNATURE-----

      reply	other threads:[~2012-11-06 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 21:14 3.7-rc2 build failure on s390x Alexander Graf
2012-10-23  6:20 ` Christian Borntraeger
2012-10-31 10:32   ` Alexander Graf
2012-11-05 13:08     ` Christian Borntraeger
2012-11-05 16:13       ` Jeff Mahoney
2012-11-06 13:02         ` Cornelia Huck
2012-11-06 19:20           ` Jeff Mahoney [this message]

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=509962F8.7040204@suse.com \
    --to=jeffm@suse.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@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.