From: Nick Andrew <nick@nick-andrew.net>
To: Andy Whitcroft <apw@canonical.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Crutcher Dunnavant <crutcher+kernel@datastacks.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] sysrq: add commentary on why we use the console loglevel over using KERN_EMERG
Date: Thu, 8 Jan 2009 19:44:04 +1100 [thread overview]
Message-ID: <20090108084404.GA26403@mail.local.tull.net> (raw)
In-Reply-To: <1231364958-26253-4-git-send-email-apw@canonical.com>
On Wed, Jan 07, 2009 at 09:49:18PM +0000, Andy Whitcroft wrote:
> Add an explanitory comment as to why we modify the kernel console
explanatory
> loglevel rather than simply moving sysrq messages to KERN_EMERG level.
>
> Signed-off-by: Andy Whitcroft <apw@canonical.com>
Nick.
next prev parent reply other threads:[~2009-01-08 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 12:37 sysrq loglevel Andy Whitcroft
2009-01-07 19:25 ` Andrew Morton
2009-01-07 20:50 ` Andy Whitcroft
2009-01-07 21:49 ` [PATCH 0/3] document sysrq interaction with loglevels Andy Whitcroft
2009-01-07 21:49 ` [PATCH 1/3] sysrq documentation: remove the redundant updated date Andy Whitcroft
2009-01-07 21:49 ` [PATCH 2/3] sysrq documentation: document why the command header only is shown Andy Whitcroft
2009-01-07 23:30 ` Randy Dunlap
2009-01-07 21:49 ` [PATCH 3/3] sysrq: add commentary on why we use the console loglevel over using KERN_EMERG Andy Whitcroft
2009-01-08 8:44 ` Nick Andrew [this message]
2009-01-08 2:10 ` [PATCH 0/3] document sysrq interaction with loglevels V2 Andy Whitcroft
2009-01-08 2:10 ` [PATCH 1/3] sysrq documentation: remove the redundant updated date Andy Whitcroft
2009-01-08 2:10 ` [PATCH 2/3] sysrq documentation: document why the command header only is shown Andy Whitcroft
2009-01-08 2:10 ` [PATCH 3/3] sysrq: add commentary on why we use the console loglevel over using KERN_EMERG Andy Whitcroft
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=20090108084404.GA26403@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=crutcher+kernel@datastacks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.