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 S1751284AbdH2RgM (ORCPT <rfc822;w@1wt.eu>);
        Tue, 29 Aug 2017 13:36:12 -0400
Received: from mail-io0-f176.google.com ([209.85.223.176]:34514 "EHLO
        mail-io0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750909AbdH2RgL (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 29 Aug 2017 13:36:11 -0400
MIME-Version: 1.0
In-Reply-To: <1504027992.2040.30.camel@perches.com>
References: <20170815025625.1977-1-sergey.senozhatsky@gmail.com>
 <20170828090521.GA25025@amd> <CA+55aFx_o_FfCO+c62zMWH8H8rLJsnKZ1TWvMqyUs2A90QJgGg@mail.gmail.com>
 <1504026634.2040.27.camel@perches.com> <CA+55aFzi_Rt6g8aS1RSvszcH6e+=HCDi1g2SDKtEY0BA+cL5VQ@mail.gmail.com>
 <1504027992.2040.30.camel@perches.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue, 29 Aug 2017 10:36:09 -0700
X-Google-Sender-Auth: 8fn-XP53V6T4v50npZ7uq6hLn0E
Message-ID: <CA+55aFz4E_zkoZvM9mO0v4cZU7Y-VZhGYRC0OzLPvB5tgqwi=w@mail.gmail.com>
Subject: Re: printk: what is going on with additional newlines?
To: Joe Perches <joe@perches.com>
Cc: Pavel Machek <pavel@ucw.cz>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Petr Mladek <pmladek@suse.com>, Steven Rostedt <rostedt@goodmis.org>,
        Jan Kara <jack@suse.cz>, Andrew Morton <akpm@linux-foundation.org>,
        Jiri Slaby <jslaby@suse.com>, Andreas Mohr <andi@lisas.de>,
        Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
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

On Tue, Aug 29, 2017 at 10:33 AM, Joe Perches <joe@perches.com> wrote:
>
> Your change broke a bunch of output.

Tough. We've done that before to force people to fix their code.

I'm actually upset that EVEN NOW (and it's been, what, 18 months),
people ask for the old broken shit behavior back.

It's ten years since we introduced the marker, and it's been over a
year since I made that pretty much a requirement, and people still
want to do the broken crap.

I'm not AT ALL feeling sorry for people. Fix your shit, or see ugly
output. Those are the two choices.

          Linus