From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755316AbcAROlj (ORCPT ); Mon, 18 Jan 2016 09:41:39 -0500 Received: from mx2.suse.de ([195.135.220.15]:32869 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754972AbcAROlh (ORCPT ); Mon, 18 Jan 2016 09:41:37 -0500 Date: Mon, 18 Jan 2016 15:41:14 +0100 From: Borislav Petkov To: =?utf-8?B?TcOlbnMgUnVsbGfDpXJk?= Cc: Thomas Voegtle , Michal Marek , Markus Trippelsdorf , linux-kernel@vger.kernel.org, x86-ml Subject: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig Message-ID: <20160118144114.GE12651@pd.tnic> References: <568FCC45.1010301@suse.cz> <20160111194311.GF4686@pd.tnic> <20160111205945.GH4686@pd.tnic> <20160111211712.GI4686@pd.tnic> <20160114184350.GB12109@pd.tnic> <20160118140649.GC12651@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 18, 2016 at 02:11:49PM +0000, Måns Rullgård wrote: > Wasn't the idea *not* to disable CONFIG_MICROCODE? Is the error message not understandable? +MSG="\nYou have CONFIG_MICROCODE enabled without BLK_DEV_INITRD. The preferred\n\ +way is to enable it and make sure microcode is added to your initrd as\n\ +explained in Documentation/x86/early-microcode.txt. This is also the\n\ +most tested method as the majority of distros do it. Alternatively, and\n\ +if you don't want to enable modules, you should make sure the microcode\n\ +is built into the kernel.\n" -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --