From: Dan Jacobson <jidanni@jidanni.org>
To: linux-kernel@vger.kernel.org
Subject: Say what the -[ cut here ]- lines are called
Date: Fri, 17 Aug 2018 05:09:10 +0800 [thread overview]
Message-ID: <878t56rpc9.fsf@jidanni.org> (raw)
The kernel should really say what the
------------[ cut here ]------------
lines are called, else users will say things like:
"I discovered that the user needs to use xrandr in _two_ steps for
certain resolutions, else he will trigger a
kernel: ------------[ cut here ]------------ line."
instead of
"...will trigger a kernel problem."
"...will trigger a kernel fault."
"...will trigger a kernel oops."
or whatever it is supposed to be called.
So say e.g.,
------------[ cut here ]------------
Kernel fault:
etc. there in the syslog. Thanks.
next reply other threads:[~2018-08-17 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 21:09 Dan Jacobson [this message]
2018-08-17 20:22 ` Randy Dunlap
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=878t56rpc9.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome