From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] sh: Modernize printing of kernel messages
Date: Tue, 3 Dec 2019 13:36:55 -0800 [thread overview]
Message-ID: <20191203213655.GA3253@roeck-us.net> (raw)
In-Reply-To: <20191203162645.19950-1-geert+renesas@glider.be>
On Tue, Dec 03, 2019 at 05:26:38PM +0100, Geert Uytterhoeven wrote:
> Hi all,
>
> This patch series fixes the broken lines in kernel output, which I
> presume have been happening since commit 4bcc595ccd80decb ("printk:
> reinstate KERN_CONT for printing continuat ion lines").
> Most annoying are the ones in call traces and disassembly dumps, as they
> cause lots of small bits of information to fly by your serial console.
>
> Thanks!
>
> Geert Uytterhoeven (7):
> sh: kernel: disassemble: Fix broken lines in disassembly dumps
> sh: dump_stack: Fix broken lines and ptrval in calltrace dumps
> sh: process: Fix broken lines in register dumps
> sh: sh2007: Modernize printing of kernel messages
> sh: pci: Modernize printing of kernel messages
> sh: machvec: Modernize printing of kernel messages
> sh: fault: Modernize printing of kernel messages
>
Yes, the output does look a bit nicer with those patches applied.
For the series:
Tested-by: Guenter Roeck <linux@roeck-us.net>
> arch/sh/boards/board-sh2007.c | 4 +-
> arch/sh/drivers/pci/common.c | 6 +-
> arch/sh/drivers/pci/pci-sh7780.c | 23 ++++---
> arch/sh/drivers/pci/pci.c | 11 ++--
> arch/sh/kernel/disassemble.c | 103 ++++++++++++++++---------------
> arch/sh/kernel/dumpstack.c | 24 +++----
> arch/sh/kernel/machvec.c | 8 +--
> arch/sh/kernel/process_32.c | 38 +++++-------
> arch/sh/mm/fault.c | 39 ++++++------
> 9 files changed, 124 insertions(+), 132 deletions(-)
>
> --
> 2.17.1
>
> 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
prev parent reply other threads:[~2019-12-03 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 16:26 [PATCH 0/7] sh: Modernize printing of kernel messages Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 1/7] sh: kernel: disassemble: Fix broken lines in disassembly dumps Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 2/7] sh: dump_stack: Fix broken lines and ptrval in calltrace dumps Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 3/7] sh: process: Fix broken lines in register dumps Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 4/7] sh: sh2007: Modernize printing of kernel messages Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 5/7] sh: pci: " Geert Uytterhoeven
2019-12-03 18:02 ` Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 6/7] sh: machvec: " Geert Uytterhoeven
2019-12-03 16:26 ` [PATCH 7/7] sh: fault: " Geert Uytterhoeven
2019-12-03 21:36 ` Guenter Roeck [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=20191203213655.GA3253@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).