From: Joe Perches <joe@perches.com>
To: check.kernel@gmail.com
Cc: Petr Mladek <pmladek@suse.cz>, Alex Elder <elder@linaro.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Peter Hurley <peter@hurleysoftware.com>,
Tejun Heo <tj@kernel.org>, Ethan du <duhui@xiaomi.com>,
Linghua Gu <gulinghua@xiaomi.com>,
linux-kernel@vger.kernel.org,
yangdongdong <yangdongdong@xiaomi.com>
Subject: Re: [PATCH v3] fs/pstore: provide panic data even in suspend
Date: Thu, 13 Aug 2015 10:53:05 -0700 [thread overview]
Message-ID: <1439488385.27506.9.camel@perches.com> (raw)
In-Reply-To: <1439351152-10836-1-git-send-email-check.kernel@gmail.com>
On Wed, 2015-08-12 at 11:45 +0800, check.kernel@gmail.com wrote:
> From: yangdongdong <yangdongdong@xiaomi.com>
>
> If system restart after panic, this patch also enables
> panic and oops messages which in suspend context to be
> logged into ramoops console buffer where it can be read
> back at some later point.
trivia:
> diff --git a/include/linux/pstore_ram.h b/include/linux/pstore_ram.h
[]
> @@ -52,6 +52,7 @@ struct persistent_ram_zone {
> size_t old_log_size;
> };
>
> +extern void emergency_unlock_console(void);
None of the other function prototypes in this file use extern.
This one shouldn't either.
> struct persistent_ram_zone *persistent_ram_new(phys_addr_t start, size_t size,
> u32 sig, struct persistent_ram_ecc_info *ecc_info,
> unsigned int memtype);
prev parent reply other threads:[~2015-08-13 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 3:45 check.kernel
2015-08-13 17:53 ` Joe Perches [this message]
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=1439488385.27506.9.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=check.kernel@gmail.com \
--cc=duhui@xiaomi.com \
--cc=elder@linaro.org \
--cc=gulinghua@xiaomi.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=peter@hurleysoftware.com \
--cc=pmladek@suse.cz \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=yangdongdong@xiaomi.com \
/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