From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from manchmal.in-ulm.de ([217.10.9.201]:34280 "EHLO
        manchmal.in-ulm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750732AbeAOUYo (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 15 Jan 2018 15:24:44 -0500
Date: Mon, 15 Jan 2018 21:24:41 +0100
From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.4 00/87] 4.4.112-stable review
Message-ID: <1516047750@msgid.manchmal.in-ulm.de>
References: <20180115123349.252309699@linuxfoundation.org>
 <20180115134718.GB31888@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180115134718.GB31888@kroah.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

Greg Kroah-Hartman wrote...

> Well, that was a brown-bag release, let's try -rc2 now!
>  	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.112-rc1.gz

Being the bringer of bad news: -rc2.gz obviously.

Also, care to explain what build error messages to expect? I saw your
message too late and ran into

arch/x86/kernel/cpu/bugs.c:58:24: error: 'X86_BUG_CPU_MELTDOWN' undeclared (first use in this function)

    Christoph