mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Mikulas Patocka <mpatocka@redhat.com>,
	Michal Januszewski <spock@gentoo.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uvesafb: use pr_cont when printing multiple parameters on the same line
Date: Thu, 29 Jun 2017 20:47:57 -0700	[thread overview]
Message-ID: <1498794477.2739.12.camel@perches.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1706292214580.21823@file01.intranet.prod.int.rdu2.redhat.com>

On Thu, 2017-06-29 at 22:16 -0400, Mikulas Patocka wrote:
> The kernel automatically inserts newlines between printk calls unless
> pr_cont is used. This patch changes the uvesafb log message from:

Should be fixed in -next already.

commit a8feae091106 ("uvesafb: Fix continuation printks without
KERN_LEVEL to pr_cont, neatening")

      reply	other threads:[~2017-06-30  3:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  2:16 Mikulas Patocka
2017-06-30  3:47 ` 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=1498794477.2739.12.camel@perches.com \
    --to=joe@perches.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=spock@gentoo.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
all inboxes | Powered by JetHome®