From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Kosina <jikos@kernel.org>,
Colin Ian King <colin.king@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] trivial for 4.9
Date: Fri, 07 Oct 2016 13:18:58 -0700 [thread overview]
Message-ID: <1475871538.1945.15.camel@perches.com> (raw)
In-Reply-To: <CA+55aFzk18SrNcAcU-Km5kXcPHqK=PT0RhwDht3vztasM-oVmg@mail.gmail.com>
On Fri, 2016-10-07 at 13:13 -0700, Linus Torvalds wrote:
> On Fri, Oct 7, 2016 at 1:04 PM, Joe Perches <joe@perches.com> wrote:
> > Any printk without a KERN_<level> prefix, and there
> > are still many of those, can cause random interleaving.
> How about people actually work on *that* instead of working around it?
> Because the above really should not be true.
> > Not at all. Until printk KERN_<level> uses are mandated,
> > then these newlines are still useful.
> The patches literally added those '\n' things to the pr_xyz() routines
> that *enforce* KERN_<level>.
No, because any of those can be followed by a bare printk
or a pr_cont that continues the original line.
> So really. It's a step backwards. We shouldn't need them. We should
> *remove* '\n' at the end, and then if that actually causes problems,
> we should fix those problems.
$ git grep -w printk * | grep -v "^tools" | grep -v KERN | wc -l
13176
Have at it but here are _far_ fewer missing newlines
and it'd be much lower churn to fix those than remove
all the newlines and fix the missing continuations.
next prev parent reply other threads:[~2016-10-07 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 8:51 [GIT PULL] trivial for 4.9 Jiri Kosina
2016-10-07 19:22 ` Linus Torvalds
2016-10-07 20:04 ` Joe Perches
2016-10-07 20:13 ` Linus Torvalds
2016-10-07 20:18 ` Joe Perches [this message]
2016-10-07 20:25 ` Linus Torvalds
2016-10-07 20:33 ` Joe Perches
2016-10-07 21:06 ` Linus Torvalds
2016-10-07 21:37 ` Linus Torvalds
2016-10-08 7:36 ` Joe Perches
2016-10-10 5:48 ` Joe Perches
2016-10-07 21:44 ` Joe Perches
2016-10-07 23:01 ` Tony Luck
2016-10-07 23:09 ` Tony Luck
2016-10-07 23:36 ` Linus Torvalds
2016-10-08 13:16 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1475871538.1945.15.camel@perches.com \
--to=joe@perches.com \
--cc=colin.king@canonical.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox