Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp876302imm; Tue, 5 Jun 2018 06:00:29 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLG+c7SF6iC+ODSnKqgrSVETdkzXchuehkuyQCkPavVNi0MOeabzzsDeGikZcQqj9kFV/Lf X-Received: by 2002:a17:902:7603:: with SMTP id k3-v6mr22969346pll.371.1528203629535; Tue, 05 Jun 2018 06:00:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528203629; cv=none; d=google.com; s=arc-20160816; b=u5giuw0+ZYVwyZkE2UZOrkDkkKNFs5/3SaimViKVUNzJaKWyHpVDroF0dMAmzs7yEF Wk4WeGfo/4GJ49ddpwn+VL6Nat5GtCVVjOOWnqoQHv9fJ72eu6CS7qCCOvSRFt6c2hTN yGYic1ssjcDaU7YWLMH2jGjDj9knG6UDhfThJOQ03kGl5ODSYUKV7TM8dIl21BlGXcRm T86hwNcmrf29ltjG6mugZ4o9CLdtaOOYZe0lTdv6oGWfxMOw7P7EAXsvidHydgL/nFEY n6DvLGYFBFZ4yUljbi1D0gBHqsVtYFg4xA8WDojP5sR+sPPOnU6/5otI7Dvmqjd0YLdV FbBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=rB54byhIwPg3tu+Y7Hv5uI/mGe6Ztf5qNWajR/xGlBM=; b=fvQRmrk28gIt/fb3gX6IlZpbsOm50zTaX7OESLuh5J6ZaVjhkHm/9Hp7mrChXWUhDP m2dnG1J7sX5WSQ6qXJqBGtMP+HHnxLvcV/6dE5iLs705g0tTFxaLneGKEEgkpHHkKcbt XkdezGKpOd27xpamyvQkyW1M7sfgBKu21ljlHIRWcDQAI5Guz1AOx/s2Jp3ADIuaKMZO IuhCcreGuUds5JhSV+tG96aoo68fwnOfkWyA7ollR7HwT9Ham7VDaMWaZQSz6HVSjq1i cFO7jPMN05GVRhxAhkdB4TdfkybtmwneRa4KHFG9j1tIqcOQfY7Ll3nP3o4EtUlrPhqP pOGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m1-v6si47410963plt.276.2018.06.05.06.00.14; Tue, 05 Jun 2018 06:00:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751788AbeFEM7p (ORCPT + 99 others); Tue, 5 Jun 2018 08:59:45 -0400 Received: from mx2.suse.de ([195.135.220.15]:41657 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751755AbeFEM7o (ORCPT ); Tue, 5 Jun 2018 08:59:44 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id AB72DACE7; Tue, 5 Jun 2018 12:59:43 +0000 (UTC) Date: Tue, 5 Jun 2018 14:59:43 +0200 From: Petr Mladek To: Joe Perches Cc: Maninder Singh , sergey.senozhatsky@gmail.com, rostedt@goodmis.org, linux-kernel@vger.kernel.org, a.sahrawat@samsung.com, pankaj.m@samsung.com, v.narang@samsung.com Subject: Re: [PATCH 1/2] printk: remove unused flag LOG_NOCONS Message-ID: <20180605125943.i3ly72liuqyopuqm@pathway.suse.cz> References: <20180531102133epcas5p2e8d47887c1708836c9b70964983093e2~zs4eTmEuv0380103801epcas5p2U@epcas5p2.samsung.com> <20180531121633.acuffu2b66q24c5c@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2018-05-31 08:12:23, Joe Perches wrote: > On Thu, 2018-05-31 at 14:16 +0200, Petr Mladek wrote: > > On Thu 2018-05-31 15:47:51, Maninder Singh wrote: > > > This patch removes unused flag LOG_NOCONS for printk. > > > usage of this flag is removed long back with below commit. > > > > Make sense. > > > > > "5c2992ee7fd8a29d04125dc0aa3522784c5fa5eb" > > > printk: remove console flushing special cases for > > > partial buffered lines > [] > > > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c > [] > > > @@ -349,10 +349,9 @@ enum con_msg_format_flags { > > > */ > > > > > > enum log_flags { > > > - LOG_NOCONS = 1, /* already flushed, do not print to console */ > > > - LOG_NEWLINE = 2, /* text ended with a newline */ > > > - LOG_PREFIX = 4, /* text started with a prefix */ > > > - LOG_CONT = 8, /* text is a fragment of a continuation line */ > > > + LOG_NEWLINE = 1, /* text ended with a newline */ > > > + LOG_PREFIX = 2, /* text started with a prefix */ > > > + LOG_CONT = 4, /* text is a fragment of a continuation line */ > > > }; > > > > Please, do not renumber the bits if there is no real need for it. > > The format of the log buffer is read also by external tool like > > "crash". It seems that "crash" ignores these flags but... > > Hmm, if it's not an internal interface, then these > definitions should probably be removed from this file > and exposed in a uapi file. "crash" is not a typical userspace tool. We break it regularly. We do not need to put the API into the stone because of "crash". On the other hand, we also need not break it if it can be avoided easily. Best Regards, Petr