From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Joe Perches <joe@perches.com>
Cc: Michal Januszewski <spock@gentoo.org>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uvesafb: Fix continuation printks without KERN_LEVEL to pr_cont, neatening
Date: Wed, 14 Jun 2017 15:44:07 +0000 [thread overview]
Message-ID: <4462877.IlSixkH9uk@amdc3058> (raw)
In-Reply-To: <c6cbf28b5763bb945d1f55b72f2b79a7772b9966.1497287034.git.joe@perches.com>
On Monday, June 12, 2017 10:05:45 AM Joe Perches wrote:
> Linus recently broke the printk without KERN_CONT behavior.
> Fix it for uvesafb.
>
> While there, convert printk(KERN_<LEVEL> to pr_<level>.
> Add pr_fmt and remove the embedded prefixes.
>
> Miscellanea:
>
> o Coalesce formats and realign arguments
> o Add a missing space to a format when coalescing.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Patch queued for 4.13, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-06-14 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170612170554epcas2p2495044e271060f3496db97dc6f31da4c@epcas2p2.samsung.com>
2017-06-12 17:05 ` [PATCH] uvesafb: Fix continuation printks without KERN_LEVEL to pr_cont, neatening Joe Perches
2017-06-14 15:44 ` Bartlomiej Zolnierkiewicz [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=4462877.IlSixkH9uk@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=joe@perches.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).