linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hari.vyas@broadcom.com (Hari Vyas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix for restoring console loglevel after handling traps
Date: Thu, 19 Jul 2018 15:18:53 +0530	[thread overview]
Message-ID: <1531993734-1463-1-git-send-email-hari.vyas@broadcom.com> (raw)

changes in v1:
	Separate functions for changing, retrieving, storing and restoring
	console loglevel messages.
	Restoring console loglevel message is done from arm64 trap handling
	code but can be extended on need basis by other user.
	Restoring is actually required in die() function only and other places
	kernel will panic but added considering code completion

Hari Vyas (1):
  arm64: fix for restoring console loglevel after handling traps

 arch/arm64/kernel/traps.c |  6 +++++-
 include/linux/printk.h    | 38 +++++++++++++++++++++++++++++++++++---
 kernel/printk/printk.c    |  3 +++
 3 files changed, 43 insertions(+), 4 deletions(-)

-- 
1.9.1

             reply	other threads:[~2018-07-19  9:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  9:48 Hari Vyas [this message]
2018-07-19  9:48 ` [PATCH] arm64: fix for restoring console loglevel after handling traps Hari Vyas
2018-07-19 10:01   ` Sergey Senozhatsky
2018-07-19 10:17     ` Hari Vyas
2018-07-19 10:39       ` Mark Rutland
2018-07-19 14:12         ` Hari Vyas
2018-07-20  6:26           ` Mark Rutland
2018-07-20  6:40             ` Sergey Senozhatsky
2018-07-20  7:31               ` Hari Vyas
2018-07-20  9:44                 ` Mark Rutland
2018-07-20 10:57                   ` Hari Vyas
2018-07-20 11:22                     ` Mark Rutland
2018-07-20 12:13           ` Petr Mladek
2018-07-20 13:34             ` Hari Vyas
2018-07-24  9:14               ` Hari Vyas
2018-07-24  9:48                 ` Mark Rutland
2018-07-25 11:13                   ` Hari Vyas
2018-07-20  9:28 ` Florian Fainelli

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=1531993734-1463-1-git-send-email-hari.vyas@broadcom.com \
    --to=hari.vyas@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).