summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorFinn Thain <fthain@telegraphics.com.au>2018-09-11 20:18:44 -0400
committerMichael Ellerman <mpe@ellerman.id.au>2018-10-08 22:53:10 +1100
commit2341629eadc4a40aa46103c7f1ff5f38459688d3 (patch)
tree7ef371c2b3b07b075d3225006403444feebaec17 /drivers/net
parent0792a2c8e0bbda3605b8d42c6b9635be7b19982a (diff)
downloadlinux-2341629eadc4a40aa46103c7f1ff5f38459688d3.tar.gz
linux-2341629eadc4a40aa46103c7f1ff5f38459688d3.tar.bz2
linux-2341629eadc4a40aa46103c7f1ff5f38459688d3.zip
macintosh/adb: Rework printk output again
Avoid the KERN_CONT problem by avoiding message fragments. The problem arises during async ADB bus probing, when ADB messages may get mixed up with other messages. See also, commit 4bcc595ccd80 ("printk: reinstate KERN_CONT for printing continuation lines"). Remove a number of printk() continuation lines by logging handler changes in adb_try_handler_change() instead. This patch addresses the problematic use of "\n" at the beginning of pr_cont() messages, which got overlooked in commit f2be6295684b ("macintosh/adb: Properly mark continued kernel messages"). That commit also changed printk(KERN_DEBUG ...) to pr_debug(...), which hinders work on low-level ADB driver bugs. Revert that change. Cc: Andreas Schwab <schwab@linux-m68k.org> Tested-by: Stan Johnson <userm57@yahoo.com> Signed-off-by: Finn Thain <fthain@telegraphics.com.au> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions