From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: randconfig errors
Date: Fri, 15 Feb 2013 19:47:43 +0100 [thread overview]
Message-ID: <c163151b4b855149ba57faa9a1a10c64@localhost> (raw)
In-Reply-To: <26e621467155fdb1626ecdac4e811deb@localhost>
On Fri, 15 Feb 2013 19:22:37 +0100, Marc Zyngier <marc.zyngier@arm.com>
wrote:
> On Fri, 15 Feb 2013 11:25:56 -0600, Rob Herring <robherring2@gmail.com>
> wrote:
>> Errors from randconfig builds restricted to multi-platform configs on
>> the current linux-next. I know I've seen a fix on the first one from
>> Arnd, but have not investigated any of these.
>>
>
>>
>
/var/lib/jenkins/jobs/linux-randconfig/workspace/include/linux/kvm_host.h:333:34:
>> error: 'KVM_USER_MEM_SLOTS' undeclared here (not in a function)
>
> This one comes from bbacc0c (KVM: Rename KVM_MEMORY_SLOTS ->
> KVM_USER_MEM_SLOTS).
> I'll queue a patch to fix the breakage...
Looks like there's a few more, and what was brewing in kvm-next had some
side effects.
Christoffer, I'll send the patches separately.
M.
--
Fast, cheap, reliable. Pick two.
next prev parent reply other threads:[~2013-02-15 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 17:25 randconfig errors Rob Herring
2013-02-15 18:00 ` Arnd Bergmann
2013-02-15 20:11 ` Mike Turquette
2013-02-15 20:28 ` Troy Kisky
2013-02-22 9:29 ` Arnd Bergmann
2013-02-15 18:22 ` Marc Zyngier
2013-02-15 18:47 ` Marc Zyngier [this message]
2013-02-15 19:16 ` Christoffer Dall
2013-02-15 19:22 ` Marc Zyngier
2013-02-15 19:24 ` Christoffer Dall
2013-02-15 19:24 ` Christoffer Dall
[not found] ` <c01a8ed845054b9d9cbddb341bac5f0e@DLEE74.ent.ti.com>
2013-02-15 19:45 ` Matt Porter
2013-02-15 20:12 ` Arnd Bergmann
2013-02-15 20:25 ` Chris Ball
2013-02-20 6:36 ` Vinod Koul
2013-02-20 9:53 ` Arnd Bergmann
2013-02-21 10:38 ` Shawn Guo
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=c163151b4b855149ba57faa9a1a10c64@localhost \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.