From: Andreas Schwab <schwab@linux-m68k•org>
To: David Laight <David.Laight@ACULAB•COM>
Cc: Benjamin Herrenschmidt <benh@au1•ibm.com>,
"linuxppc-dev\@ozlabs.org" <linuxppc-dev@ozlabs•org>
Subject: Re: [PATCH v2] adb: properly mark continued kernel messages
Date: Wed, 30 Nov 2016 18:58:07 +0100 [thread overview]
Message-ID: <8760n4df4g.fsf@linux-m68k.org> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB02303EA@AcuExch.aculab.com> (David Laight's message of "Wed, 30 Nov 2016 14:50:41 +0000")
On Nov 30 2016, David Laight <David.Laight@ACULAB•COM> wrote:
> Doesn't pr_cont() have its own major problem - garbled messages if
> there are concurrent writers?
> So it is best avoided if at all possible.
You are free to submit a followup patch the rework the messaging. My
patch is a strict improvement.
Andreas.
--
Andreas Schwab, schwab@linux-m68k•org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-11-30 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 13:22 [PATCH] adb: properly mark continued kernel messages Andreas Schwab
2016-11-26 22:43 ` Benjamin Herrenschmidt
2016-11-28 20:29 ` [PATCH v2] " Andreas Schwab
2016-11-30 14:50 ` David Laight
2016-11-30 17:58 ` Andreas Schwab [this message]
2016-12-02 4:10 ` Michael Ellerman
2018-01-29 4:13 ` [v2] " Michael Ellerman
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=8760n4df4g.fsf@linux-m68k.org \
--to=schwab@linux-m68k$(echo .)org \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=benh@au1$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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