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=-5.2 required=3.0 tests=BAYES_00, BUG6152_INVALID_DATE_TZ_ABSURD,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU, HEADER_FROM_DIFFERENT_DOMAINS,INVALID_DATE_TZ_ABSURD,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 3664FC1B0E3 for ; Tue, 8 Dec 2020 07:43:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1B18F23A51 for ; Tue, 8 Dec 2020 07:43:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727772AbgLHHnl (ORCPT ); Tue, 8 Dec 2020 02:43:41 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:37174 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727483AbgLHHnk (ORCPT ); Tue, 8 Dec 2020 02:43:40 -0500 From: John Ogness DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1607413378; 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: in-reply-to:in-reply-to:references:references; bh=4FiUfOe1m4zmK5rloas3mUpAaYXEafQsN3Pdg2nM09g=; b=melhXpYO30SCRb7mdPnLU8RCJpJt3Qve8Hx00aMH1lc/7t6/6aZTYab8iRNi8FNj7k9MBd WyWcmqe+cxnXiRmdf5O8+oAM09GAU1nbpoDO6fjtpnWA/KxyQ8iupCsBWOOq8czX2qtoFx fuV7pkqJ93HOSB8O9UzKL2r0iODGrBS3ASciVUGBlHO+RXDUERmYmg6w+5EY7znrK9Nl7q TFYEX7rvGcuFNUyZ51RqDHUmXwW54l6eMVDv/U7wmG4RnsqDMu05AI6uQ4tNvTuJRNuHz0 RurdlM2LpwN2bImyyusQCizug6eqHDZ55cBsXd8gvsC/jGcdjvhvvdr/nOOong== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1607413378; 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: in-reply-to:in-reply-to:references:references; bh=4FiUfOe1m4zmK5rloas3mUpAaYXEafQsN3Pdg2nM09g=; b=r4FvqJ+deb819UadigBkS9YoOBzZ23ieBW/86XIczrge0NYbu5pIwnDMEvj2+kevd1AkqU C3lLmFy83wM6flDA== To: Petr Mladek Cc: Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH next v3 2/3] printk: define CONSOLE_LOG_MAX in printk.h In-Reply-To: <20201207222020.2923-3-john.ogness@linutronix.de> References: <20201207222020.2923-1-john.ogness@linutronix.de> <20201207222020.2923-3-john.ogness@linutronix.de> Date: Tue, 08 Dec 2020 08:48:57 +0106 Message-ID: <87k0tsd9q6.fsf@jogness.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-12-07, John Ogness wrote: > CONSOLE_EXT_LOG_MAX for extended console messages is already defined > in printk.h. Define CONSOLE_LOG_MAX there as well so that future > changes can make use of the constant for non-extended console > messages. Actually this patch is not necessary for this series. Also, this patch should probably modify all the "LOG_LINE_MAX + PREFIX_MAX" calls as well. John Ogness