From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Guenter Roeck <private@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: Stable release queue build failures (3.18, 4.1)
Date: Wed, 23 May 2018 01:28:46 +0000 [thread overview]
Message-ID: <20180523012845.GN8514@sasha-vm> (raw)
In-Reply-To: <4cbcb711-0f87-1fc3-16ab-689285aa09ca@roeck-us.net>
On Mon, May 21, 2018 at 07:48:53AM -0700, Guenter Roeck wrote:
>v3.18.109-42-g6009175, s390:allnoconfig:
>
>arch/s390/mm/vmem.c:30:20: warning: 'vmem_alloc_pages' defined but not used [-Wunused-function]
>arch/s390/kernel/irq.c: Assembler messages:
>arch/s390/kernel/irq.c:180: Error: Unrecognized opcode: `brasl'
>
>v4.1.51-555-g5b61994, {i386,x86_64}:{allyesconfig,allmodconfig}:
>
>arch/x86/kvm/vmx.c: In function 'vmx_handle_external_intr': arch/x86/kvm/vmx.c:8016:4: error: expected ':' or ')' before 'CALL_NOSPEC'
>
>Guenter
>
Fixed, thank you!
prev parent reply other threads:[~2018-05-23 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 14:48 Stable release queue build failures (3.18, 4.1) Guenter Roeck
2018-05-21 16:35 ` Greg Kroah-Hartman
2018-05-23 1:28 ` Sasha Levin [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=20180523012845.GN8514@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=private@roeck-us.net \
--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 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.