From: Andrew Lunn <andrew@lunn.ch>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: add "8<--- cut here ---" to kernel dumps
Date: Tue, 29 Jan 2019 16:33:34 +0100 [thread overview]
Message-ID: <20190129153334.GO4765@lunn.ch> (raw)
In-Reply-To: <E1goUA9-0003OK-TE@rmk-PC.armlinux.org.uk>
On Tue, Jan 29, 2019 at 02:14:53PM +0000, Russell King wrote:
> Add a "8<--- cut here ---" marker to kernel dumps to help users cut
> the dump at the right place when emailing list, rather than cutting
> off the first line which gives the reason for the dump.
Hi Russell
Good idea.
Is it worth also putting a marked at the end? I sometime get crash
dumps with the stack trace chopped off.
Thanks
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-29 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 14:14 [PATCH] ARM: add "8<--- cut here ---" to kernel dumps Russell King
2019-01-29 15:33 ` Andrew Lunn [this message]
2019-01-29 15:39 ` Russell King - ARM Linux admin
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=20190129153334.GO4765@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
/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