From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] printk: Create pr_<level> functions
Date: Tue, 09 Aug 2016 10:38:47 -0700 [thread overview]
Message-ID: <1470764327.14552.8.camel@perches.com> (raw)
In-Reply-To: <CAMuHMdW3ViYfJ1hRrSVSZJ9uY9OXttHU86H-ZmRwMSiZ+xJ40A@mail.gmail.com>
On Tue, 2016-08-09 at 19:01 +0200, Geert Uytterhoeven wrote:
> On Fri, Jun 24, 2016 at 5:46 AM, Joe Perches <joe@perches.com> wrote:
> > Using functions instead of macros can reduce overall code size
> > by eliminating unnecessary "KERN_SOH" prefixes from
> > format strings.
> This change, commit 874f9c7da9a4acbc1 upstream, seems to have an
> (unintendent?) side-effect.
>
> Before, pr_*() calls without a trailing newline characters would be printed
> with a newline character appended, both on the console and in the output
> of the dmesg command.
> After this commit, no new line character is appended, and the output of
> the next pr_*() call of the same type may be appended, like in:
>
> - Truncating RAM at 0x0000000040000000-0x00000000c0000000 to
> -0x0000000070000000
> - Ignoring RAM at 0x0000000200000000-0x0000000240000000 (!CONFIG_HIGHMEM)
> + Truncating RAM at 0x0000000040000000-0x00000000c0000000 to
> -0x0000000070000000Ignoring RAM at
> 0x0000000200000000-0x0000000240000000 (!CONFIG_HIGHMEM)
>
> I don't know why this is happening, hence I had to use git bisect to find
> the offending commit.
The newline handling code inside vprintk_emit is a bit
involved and for now I suggest a revert until this has
all the same behavior as earlier.
prev parent reply other threads:[~2016-08-09 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 21:58 [PATCH V2] printk: Create pr_<level> functions Joe Perches
2016-06-24 3:46 ` [PATCH V3] " Joe Perches
2016-08-09 17:01 ` Geert Uytterhoeven
2016-08-09 17:09 ` Joe Perches
2016-08-09 17:38 ` Joe Perches [this message]
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=1470764327.14552.8.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).