From: Valdis.Kletnieks@vt.edu
To: Sergiu Iordache <sergiu@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Samo Pogacnik <samo_pogacnik@t-2.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Randy Dunlap <randy.dunlap@oracle.com>,
Marco Stornelli <marco.stornelli@gmail.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char drivers: Ram oops kernel configuration parameters
Date: Thu, 23 Jun 2011 15:59:32 -0400 [thread overview]
Message-ID: <62229.1308859172@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 23 Jun 2011 11:36:00 PDT." <1308854160-16022-1-git-send-email-sergiu@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
On Thu, 23 Jun 2011 11:36:00 PDT, Sergiu Iordache said:
> Ramoops currently has module parameters for setting the configuration
> variables (ram start, ram size and dump oopses). This makes it difficult to
> configure when the module is compiled as a builtin.
Can't you add 'ramoops.ram_start=128M ramoops.ram_size=64M' or similar
to your kernel cmdline?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-06-23 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 18:36 Sergiu Iordache
2011-06-23 18:39 ` Marco Stornelli
2011-06-23 19:59 ` Valdis.Kletnieks [this message]
2011-06-23 20:43 ` Sergiu Iordache
2011-06-23 21:33 ` Greg KH
2011-06-23 22:07 ` Mandeep Singh Baines
2011-06-24 10:49 ` Marco Stornelli
2011-06-24 17:06 ` Mandeep Singh Baines
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=62229.1308859172@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=darwish.07@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=samo_pogacnik@t-2.net \
--cc=seiji.aguchi@hds.com \
--cc=sergiu@chromium.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
all inboxes | Powered by JetHome®