From: Marco Stornelli <marco.stornelli@gmail.com>
To: Sergiu Iordache <sergiu@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] char drivers: ramoops dump_oops platform data
Date: Fri, 01 Jul 2011 20:08:34 +0200 [thread overview]
Message-ID: <4E0E0D22.4020008@gmail.com> (raw)
In-Reply-To: <1309483720-1407-2-git-send-email-sergiu@chromium.org>
Il 01/07/2011 03:28, Sergiu Iordache ha scritto:
> The platform driver currently allows setting the mem_size and mem_address.
> Since dump_oops is also a module parameter it would be more consistent
> if it could be set through platform data as well.
>
> Change-Id: I27e541a51c9722047c4163bf408e778caa77ecc9
> Signed-off-by: Sergiu Iordache<sergiu@chromium.org>
> ---
Acked-by: Marco Stornelli <marco.stornelli@gmail.com>
next prev parent reply other threads:[~2011-07-01 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 1:28 [PATCH v2 0/3] char drivers: ramoops improvements Sergiu Iordache
2011-07-01 1:28 ` [PATCH v2 1/3] char drivers: ramoops dump_oops platform data Sergiu Iordache
2011-07-01 18:08 ` Marco Stornelli [this message]
2011-07-01 1:28 ` [PATCH v2 2/3] char drivers: ramoops record_size module parameter Sergiu Iordache
2011-07-01 17:57 ` Marco Stornelli
2011-07-01 18:41 ` Sergiu Iordache
2011-07-02 8:04 ` Marco Stornelli
2011-07-06 17:08 ` Sergiu Iordache
2011-07-01 1:28 ` [PATCH v2 3/3] char drivers: ramoops debugfs entry Sergiu Iordache
2011-07-01 18:08 ` Marco Stornelli
2011-07-01 18:38 ` Sergiu Iordache
2011-07-02 8:01 ` Marco Stornelli
2011-07-02 9:01 ` Sergiu Iordache
2011-07-02 11:59 ` Marco Stornelli
2011-07-06 17:18 ` Sergiu Iordache
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=4E0E0D22.4020008@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=darwish.07@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--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