From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932511AbcHIRBF (ORCPT <rfc822;w@1wt.eu>);
	Tue, 9 Aug 2016 13:01:05 -0400
Received: from mail-it0-f67.google.com ([209.85.214.67]:36456 "EHLO
	mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751821AbcHIRBE (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Aug 2016 13:01:04 -0400
MIME-Version: 1.0
In-Reply-To: <1466739971-30399-1-git-send-email-joe@perches.com>
References: <e16cc34479dfefcae37c98b481e6646f0f69efc3.1466718827.git.joe@perches.com>
 <1466739971-30399-1-git-send-email-joe@perches.com>
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Tue, 9 Aug 2016 19:01:03 +0200
X-Google-Sender-Auth: rusj5JxjaFBB0gNwnuXdZtboU1o
Message-ID: <CAMuHMdW3ViYfJ1hRrSVSZJ9uY9OXttHU86H-ZmRwMSiZ+xJ40A@mail.gmail.com>
Subject: Re: [PATCH V3] printk: Create pr_<level> functions
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Joe,

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<digit>" 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.

Was this change intentional?
I guess it wouldn't hurt to send patches to add an explicit trailing newline
characters to messages that lack it?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds