All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/3] char drivers: rammops improvements
Date: Thu, 07 Jul 2011 19:32:49 +0200	[thread overview]
Message-ID: <4E15EDC1.7020304@gmail.com> (raw)
In-Reply-To: <1309994990-4729-1-git-send-email-sergiu@chromium.org>

Il 07/07/2011 01:29, Sergiu Iordache ha scritto:
> Improves the ramoops module by adding a dump_oops to the platform
> data, adding a record_size parameter and adding a debugfs for memory
> area access.
>
> The patch was built on the 2.6.38 kernel and is based on the following
> patches which were applied from the mmotm tree:
> ramoops-add-new-line-to-each-print
> ramoops-use-module-parameters-instead-of-platform-data-if-not-available
> ramoops-use-module-parameters-instead-of-platform-data-if-not-available-checkpatch-fixes
>
> This series is different from the initial two by being built on the ramoops modifications present in the mmotm tree and by using a different
> approach regarding the debugfs entry.
>
> The changes were tested on a CR-48 machine using the 2.6.38 kernel.
>
> Sergiu Iordache (3):
>    char drivers: ramoops dump_oops platform data
>    char drivers: ramoops record_size module parameter
>    char drivers: ramoops debugfs entry
>
>   drivers/char/ramoops.c  |  151 +++++++++++++++++++++++++++++++++++++++++++----
>   include/linux/ramoops.h |    2 +
>   2 files changed, 142 insertions(+), 11 deletions(-)
>

The patch series is ok for me.

Marco

      parent reply	other threads:[~2011-07-07 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 23:29 [PATCH v3 0/3] char drivers: rammops improvements Sergiu Iordache
2011-07-06 23:29 ` [PATCH v3 1/3] char drivers: ramoops dump_oops platform data Sergiu Iordache
2011-07-06 23:29 ` [PATCH v3 2/3] char drivers: ramoops record_size module parameter Sergiu Iordache
2011-07-06 23:29 ` [PATCH v3 3/3] char drivers: ramoops debugfs entry Sergiu Iordache
2011-07-07 20:01   ` Andrew Morton
2011-07-07 22:34     ` Sergiu Iordache
2011-07-07 22:54       ` Andrew Morton
2011-07-07 23:16         ` Sergiu Iordache
2011-07-07 23:27           ` Andrew Morton
2011-07-07 23:33             ` Greg KH
2011-07-08  6:43               ` Marco Stornelli
2011-07-11 16:54                 ` Sergiu Iordache
2011-07-12  6:41                   ` Marco Stornelli
2011-07-29  0:15                     ` Sergiu Iordache
2011-07-29  8:21                       ` Marco Stornelli
2011-07-07 17:32 ` Marco Stornelli [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=4E15EDC1.7020304@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.