From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B776CC43381 for ; Wed, 27 Mar 2019 10:18:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8722020700 for ; Wed, 27 Mar 2019 10:18:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="ASt0g41f" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733197AbfC0KSQ (ORCPT ); Wed, 27 Mar 2019 06:18:16 -0400 Received: from mail.skyhub.de ([5.9.137.197]:35678 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731904AbfC0KSP (ORCPT ); Wed, 27 Mar 2019 06:18:15 -0400 Received: from zn.tnic (p200300EC2F098000329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f09:8000:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 7B3C91EC0513; Wed, 27 Mar 2019 11:18:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553681894; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=XpCEzMyjx7ggizZrzRsQC5sDjf4G3AU/LAu6FL1x6jc=; b=ASt0g41fFYRemv28OU20I04+9BUVfdTQE5TrRpmsYZcdaHIX54Fyawrg6vVBAawB4Df6vw 8rYZc2r7br01ki44pyACXeU2p3qfUfgssCQPonVvmXAuHA/tfEbYBVGMlcETcjMvBnOq9I lPvqhKXS3hHxi05cdifAySTqjA4QATM= Date: Wed, 27 Mar 2019 11:18:15 +0100 From: Borislav Petkov To: Leon Romanovsky Cc: Joe Perches , "Rafael J . Wysocki" , Thomas Gleixner , Ingo Molnar , x86 , "H. Peter Anvin" , linux-pm , LKML Subject: Re: [PATCH -next v1] x86/apic: Reduce print level of CPU limit announcement Message-ID: <20190327101815.GB32571@zn.tnic> References: <20190327090905.5588-1-leon@kernel.org> <20190327093844.GO22899@mtr-leonro.mtl.com> <55774b1a8c82e94b2796c992889929f1da905d9b.camel@perches.com> <20190327095337.GP22899@mtr-leonro.mtl.com> <20190327101133.GQ22899@mtr-leonro.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190327101133.GQ22899@mtr-leonro.mtl.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 27, 2019 at 12:11:33PM +0200, Leon Romanovsky wrote: > ok, I tested your variant and it still prints a t least on my systems, Probably because your loglevel is set to debug. And no, we don't want to have to enable some config option in order to see this. Also, the ugly linebreak needs to go. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.