From: Wang Long <long.wanglong@huawei.com>
To: <keescook@chromium.org>, <ccross@android.com>, <anton@enomsg.org>,
<tony.luck@intel.com>, <tony@atomide.com>
Cc: <linux-kernel@vger.kernel.org>, <long.wanglong@huawei.com>,
<peifeiyue@huawei.com>, <morgan.wang@huawei.com>,
<sergiu@chromium.org>, <salyzyn@android.com>,
<anton.vorontsov@linaro.org>, <marco.stornelli@gmail.com>
Subject: [PATCH] ramoops: make it possible to change mem_type param.
Date: Fri, 27 Mar 2015 09:19:18 +0000 [thread overview]
Message-ID: <1427447958-42138-1-git-send-email-long.wanglong@huawei.com> (raw)
If we set ramoops.mem_type=1 in command line, the current
code can not change mem_type to 1, because it is assigned
to 0 in function ramoops_register_dummy.
This patch make it possible to change mem_type parameter
in command line.
Signed-off-by: Wang Long <long.wanglong@huawei.com>
---
fs/pstore/ram.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 44a549b..65e0532 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -65,7 +65,7 @@ module_param(mem_size, ulong, 0400);
MODULE_PARM_DESC(mem_size,
"size of reserved RAM used to store oops/panic logs");
-static unsigned int mem_type;
+static unsigned int mem_type = 0;
module_param(mem_type, uint, 0600);
MODULE_PARM_DESC(mem_type,
"set to 1 to try to use unbuffered memory (default 0)");
@@ -608,7 +608,7 @@ static void ramoops_register_dummy(void)
dummy_data->mem_size = mem_size;
dummy_data->mem_address = mem_address;
- dummy_data->mem_type = 0;
+ dummy_data->mem_type = mem_type;
dummy_data->record_size = record_size;
dummy_data->console_size = ramoops_console_size;
dummy_data->ftrace_size = ramoops_ftrace_size;
--
1.8.3.4
next reply other threads:[~2015-03-27 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:19 Wang Long [this message]
2015-03-30 16:31 ` Tony Lindgren
2015-03-31 1:22 ` long.wanglong
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=1427447958-42138-1-git-send-email-long.wanglong@huawei.com \
--to=long.wanglong@huawei.com \
--cc=anton.vorontsov@linaro.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=morgan.wang@huawei.com \
--cc=peifeiyue@huawei.com \
--cc=salyzyn@android.com \
--cc=sergiu@chromium.org \
--cc=tony.luck@intel.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®