[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231106204026.78940dfe@gandalf.local.home>
Date: Mon, 6 Nov 2023 20:40:26 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: jim.cromie@...il.com
Cc: Ćukasz Bartosik <lb@...ihalf.com>,
Jason Baron <jbaron@...mai.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Guenter Roeck <groeck@...gle.com>,
Yaniv Tzoreff <yanivt@...gle.com>,
Benson Leung <bleung@...gle.com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
Pekka Paalanen <ppaalanen@...il.com>,
Sean Paul <seanpaul@...omium.org>,
Daniel Vetter <daniel@...ll.ch>, linux-kernel@...r.kernel.org,
upstream@...ihalf.com, pmladek@...e.com,
sergey.senozhatsky@...il.com, john.ogness@...utronix.de,
Simon Ser <contact@...rsion.fr>
Subject: Re: [PATCH v1 05/12] tracefs: add TP_printk_no_nl - RFC
On Fri, 3 Nov 2023 21:40:13 -0600
jim.cromie@...il.com wrote:
> Steve,
> IIRC you considered adding \n where needed.
> is there anything gained (conceivably) by not just adding the trailing
> \n when "needed" ?
> statistically, macros could get us to 99.99+ "compliance"
> IIRC - the "needed" seems correct.
>
I replied to the next patch suggesting to do this on the read side.
-- Steve
Powered by blists - more mailing lists