All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	kyungmin.park@samsung.com, stevie.trujillo@gmail.com,
	xiyou.wangcong@gmail.com
Subject: Re: [PATCH 1/2 v3] ramoops: use module parameters instead of platform data if not available
Date: Wed, 08 Jun 2011 21:52:21 +0200	[thread overview]
Message-ID: <4DEFD2F4.5000403@gmail.com> (raw)
In-Reply-To: <4DEE56AF.1040601@gmail.com>

Il 07/06/2011 18:49, Marco Stornelli ha scritto:
> From: Marco Stornelli<marco.stornelli@gmail.com>
>
> Use generic module parameters instead of platform data, if platform
> data are not available. This limitation has been introduced with
> commit c3b92ce9e75f6353104fc7f8e32fb9fdb2550ad0.
>
> Signed-off-by: Marco Stornelli<marco.stornelli@gmail.com>
> CC: Kyungmin Park<kyungmin.park@samsung.com>
> CC: Américo Wang<xiyou.wangcong@gmail.com>
> Reported-by: Stevie Trujillo<stevie.trujillo@gmail.com>
> ---

Stephen,

can you add this patch and "[PATCH 2/2 v3] ramoops: add a new line for 
each print" to the linux-next? Thanks.

Regards,

Marco

  parent reply	other threads:[~2011-06-08 19:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28  9:01 [PATCH] ramoops: use module parameters instead of platform data if not available Marco Stornelli
2011-05-28 10:05 ` Stevie Trujillo
2011-05-28 14:18   ` Marco Stornelli
2011-05-28 14:48 ` [PATCH 1/2 v2] " Marco Stornelli
2011-06-06 16:02   ` Américo Wang
2011-06-07 16:49   ` [PATCH 1/2 v3] " Marco Stornelli
2011-06-08 16:01     ` Américo Wang
2011-06-08 19:52     ` Marco Stornelli [this message]
2011-06-09  0:59       ` Stephen Rothwell
2011-06-09  1:02         ` Américo Wang
2011-06-09  6:46           ` Marco Stornelli
2011-06-18 14:01     ` Marco Stornelli

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=4DEFD2F4.5000403@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stevie.trujillo@gmail.com \
    --cc=xiyou.wangcong@gmail.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 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.