Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752640AbbF2HKw (ORCPT ); Mon, 29 Jun 2015 03:10:52 -0400 Received: from mail-wg0-f46.google.com ([74.125.82.46]:36515 "EHLO mail-wg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752113AbbF2HKp (ORCPT ); Mon, 29 Jun 2015 03:10:45 -0400 Date: Mon, 29 Jun 2015 09:10:39 +0200 From: Ingo Molnar To: Alexander Kuleshov Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] x86/Kconfig.debug: make X86_VERBOSE_BOOTUP depends on EARLY_PRINTK Message-ID: <20150629071039.GA18239@gmail.com> References: <1435410167-18099-1-git-send-email-kuleshovmail@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1435410167-18099-1-git-send-email-kuleshovmail@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 697 Lines: 19 * Alexander Kuleshov wrote: > The X86_VERBOSE_BOOTUP enables informational output during the > decompression stage with the earlyprintk. If CONFIG_EARLY_PRINTK > is not set, there are no reasons to make CONFIG_X86_VERBOSE_BOOTUP > possible for the configuration. So exactly where does the code triggered by CONFIG_X86_VERBOSE_BOOTUP depend on earlyprintk? I don't see the current kernel doing that anywhere. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/